Unified desktop big brother applications

ABSTRACT

Methods and devices for selectively presenting a user interface or “desktop” across two devices are provided. More particularly, a unified desktop is presented across a device and a computer system that comprise a unified system. The unified desktop acts as a single user interface that presents data and receives user interaction in a seamless environment that emulates a personal computing environment. To function within the personal computing environment, the unified desktop includes a process for docking and undocking the device with the computer system. The unified desktop presents a new user interface to allow access to functions of the unified desktop.

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 13/627,690, filed Sep. 26, 2012, of the same title,which is a continuation-in-part and claims the benefit of and priorityto U.S. patent application Ser. No. 13/605,740, filed Sep. 6, 2012; U.S.patent application Ser. No. 13/605,482, filed Sep. 6, 2012; U.S. patentapplication Ser. No. 13/605,145, filed Sep. 6, 2012; U.S. patentapplication Ser. No. 13/604,960, filed Sep. 6, 2012; U.S. patentapplication Ser. No. 13/604,384, filed Sep. 5, 2012; U.S. patentapplication Ser. No. 13/603,136, filed Sep. 4, 2012; U.S. patentapplication Ser. No. 13/566,336, filed Aug. 3, 2012; U.S. patentapplication Ser. No. 13/566,244, filed Aug. 3, 2012; U.S. patentapplication Ser. No. 13/566,168, filed Aug. 3, 2012; U.S. patentapplication Ser. No. 13/566,103, filed Aug. 3, 2012; U.S. patentapplication Ser. No. 13/543,678, filed Jul. 6, 2012; U.S. patentapplication Ser. No. 13/543,635, filed Jul. 6, 2012; U.S. patentapplication Ser. No. 13/408,530, filed Feb. 29, 2012; U.S. patentapplication Ser. No. 13/410,931, filed Mar. 2, 2012; U.S. patentapplication Ser. No. 13/410,958, filed Mar. 2, 2012; U.S. patentapplication Ser. No. 13/410,983, filed Mar. 2, 2012; U.S. patentapplication Ser. No. 13/411,034, filed Mar. 2, 2012; U.S. patentapplication Ser. No. 13/411,075, filed Mar. 2, 2012; U.S. patentapplication Ser. No. 13/436,593, filed Mar. 30, 2012; U.S. patentapplication Ser. No. 13/436,823, filed Mar. 30, 2012; U.S. patentapplication Ser. No. 13/436,826, filed Mar. 30, 2012; U.S. patentapplication Ser. No. 13/485,734, filed May 31, 2012, and U.S. patentapplication Ser. No. 13/485,743, filed May 31, 2012.

This application also claims the benefits of and priority, under 35U.S.C. § 119(e), to U.S. Provisional Application Ser. No. 61/539,884,filed Sep. 27, 2011. This application is also related to U.S. patentapplication Ser. No. 13/217,108, filed on Aug. 24, 2011; Ser. No.13/251,427, filed on Oct. 3, 2011; Ser. No. 13/247,166, filed on Sep.28, 2011; Ser. No. 13/217,121, filed on Aug. 24, 2011; Ser. No.13/217,130, filed on Aug. 24, 2011; Ser. No. 13/247,170, filed on Sep.28, 2011; Ser. No. 13/246,669, filed on Sep. 27, 2011; Ser. No.13/217,099, filed on Aug. 24, 2011; Ser. No. 13/247,885, filed on Sep.28, 2011; Ser. No. 13/250,764, filed on Sep. 30, 2011; Ser. No.13/251,434, filed on Oct. 3, 2011; Ser. No. 13/399,901, filed on Feb.17, 2012; Ser. No. 13/399,929, filed on Feb. 17, 2012; Ser. No.13/399,936, filed on Feb. 17, 2012; Ser. No. 13/246,118, filed on Sep.27, 2011; Ser. No. 13/246,128, filed on Sep. 27, 2011; Ser. No.13/246,133, filed on Sep. 27, 2011; Ser. No. 13/246,675, filed on Sep.27, 2011 and Ser. No. 13/246,665, filed on Sep. 27, 2011. The entiredisclosure of all the applications or patents listed herein are herebyincorporated by reference, for all that they teach and for all purposes.

BACKGROUND

A substantial number of handheld computing devices, such as cellularphones, tablets, and E-Readers, make use of a touch screen display notonly to deliver display information to the user but also to receiveinputs from user interface commands. While touch screen displays mayincrease the configurability of the handheld device and provide a widevariety of user interface options, this flexibility typically comes at aprice. The dual use of the touch screen to provide content and receiveuser commands, while flexible for the user, may obfuscate the displayand cause visual clutter, thereby leading to user frustration and lossof productivity.

The small form factor of handheld computing devices requires a carefulbalancing between the displayed graphics and the area provided forreceiving inputs. On the one hand, the small display constrains thedisplay space, which may increase the difficulty of interpreting actionsor results. On the other hand, a virtual keypad or other user interfacescheme is superimposed on or positioned adjacent to an executingapplication, requiring the application to be squeezed into an evensmaller portion of the display.

This balancing act is particularly difficult for single display touchscreen devices. Single display touch screen devices are crippled bytheir limited screen space. When users are entering information into thedevice, through the single display, the ability to interpret informationin the display can be severely hampered, particularly when a complexinteraction between display and interface is required.

Current handheld computing devices may be connected to larger computingdevices, e.g., personal computers (PCs), or peripheral screens toprovide more display area. Current handheld devices do not includefeatures that allow them to provide both PC functionality and thefunctionality associated with the handheld device, e.g., phone, text, orother communication functionality. Instead, a peripheral screenconnected to a handheld device merely provides more display area for thehandheld computing device. When connecting the handheld device toanother computing system, such as a PC, the handheld device is typicallyrecognized by the computing system as a peripheral device. Thefunctionality of the handheld device is typically not integrated withthe functionality of the larger computing system.

SUMMARY

There is a need for a dual multi-display handheld computing device thatprovides for enhanced power and/or versatility compared to conventionalsingle display handheld computing devices. These and other needs areaddressed by the various aspects, embodiments, and/or configurations ofthe present disclosure. Also, while the disclosure is presented in termsof exemplary embodiments, it should be appreciated that individualaspects of the disclosure can be separately claimed.

Embodiments provide for a handheld device with a unified desktop forintegrating the functionality of the handheld device with a largercomputing system, e.g., a PC. When connected to a peripheral displayand/or a display of a PC, the handheld device provides a unified desktopdisplayed across the screen(s) of the handheld device and the additionaldisplay. The unified desktop unifies the PC functionality provided onthe additional display with the handheld functionality, such ascommunication applications (e.g., phone, SMS, MMS) provided on thescreen(s) of the handheld device. A user can seamlessly interact withapplications, e.g., open, drag, close, receive notifications, on theunified desktop whether the applications are displayed on the screens ofthe handheld device, or the peripheral display of the larger computingsystem. Each portion of the unified desktop (i.e., the portion on thehandheld device and the portion on the peripheral screen) may displaydifferent applications, information, and/or have a different layout.Also, in embodiments, each portion of the desktop may display similarinformation in different formats. For example, battery level of thehandheld device, wireless network signal strength, notifications, can bedisplayed in both portions of the desktop, with a larger format beingused on the portion of the unified desktop displayed on the peripheralscreen, and a smaller format used on the screen(s) of the peripheraldevice.

Further embodiments provide for devices, computer-executableinstructions, and methods for providing a unified desktop. Upon dockinga device with a computer system, a unified system generates a unifieddesktop. The unified desktop can include a first user interfaceassociated with the device and a second user interface associated withthe computer system. While docked, the unified system can receive afirst input. The first input may move an application display of a firstapplication from a first user interface to a second user interface. Theunified system may then re-execute the first application in a bigbrother application.

The phrases “at least one”, “one or more”, and “and/or” are open-endedexpressions that are both conjunctive and disjunctive in operation. Forexample, each of the expressions “at least one of A, B and C”, “at leastone of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B,or C” and “A, B, and/or C” means A alone, B alone, C alone, A and Btogether, A and C together, B and C together, or A, B and C together.

The term “a” or “an” entity refers to one or more of that entity. Assuch, the terms “a” (or “an”), “one or more” and “at least one” can beused interchangeably herein. It is also to be noted that the terms“comprising”, “including”, and “having” can be used interchangeably.

The term “automatic” and variations thereof, as used herein, refers toany process or operation done without material human input when theprocess or operation is performed. However, a process or operation canbe automatic, even though performance of the process or operation usesmaterial or immaterial human input, if the input is received beforeperformance of the process or operation. Human input is deemed to bematerial if such input influences how the process or operation will beperformed. Human input that consents to the performance of the processor operation is not deemed to be “material”.

The term “computer-readable medium” as used herein refers to anytangible storage and/or transmission medium that participate inproviding instructions to a processor for execution. Such a medium maytake many forms, including but not limited to, non-volatile media,volatile media, and transmission media. Non-volatile media includes, forexample, NVRAM, or magnetic or optical disks. Volatile media includesdynamic memory, such as main memory. Common forms of computer-readablemedia include, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, or any other magnetic medium, magneto-optical medium, aCD-ROM, any other optical medium, punch cards, paper tape, any otherphysical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, a solid state medium like a memory card, any other memorychip or cartridge, a carrier wave as described hereinafter, or any othermedium from which a computer can read. A digital file attachment toe-mail or other self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. When the computer-readable media is configured as a database, itis to be understood that the database may be any type of database, suchas relational, hierarchical, object-oriented, and/or the like.Accordingly, the disclosure is considered to include a tangible storagemedium or distribution medium and prior art-recognized equivalents andsuccessor media, in which the software implementations of the presentdisclosure are stored.

The term “desktop” refers to a metaphor used to portray systems. Adesktop is generally considered a “surface” that typically includespictures, called icons, widgets, folders, etc. that can activate showapplications, windows, cabinets, files, folders, documents, and othergraphical items. The icons are generally selectable to initiate a taskthrough user interface interaction to allow a user to executeapplications or conduct other operations.

The term “screen,” “touch screen,” or “touchscreen” refers to a physicalstructure that includes one or more hardware components that provide thedevice with the ability to render a user interface and/or receive userinput. A screen can encompass any combination of gesture capture region,a touch sensitive display, and/or a configurable area. The device canhave one or more physical screens embedded in the hardware. However ascreen may also include an external peripheral device that may beattached and detached from the device. In embodiments, multiple externaldevices may be attached to the device. Thus, in embodiments, the screencan enable the user to interact with the device by touching areas on thescreen and provides information to a user through a display. The touchscreen may sense user contact in a number of different ways, such as bya change in an electrical parameter (e.g., resistance or capacitance),acoustic wave variations, infrared radiation proximity detection, lightvariation detection, and the like. In a resistive touch screen, forexample, normally separated conductive and resistive metallic layers inthe screen pass an electrical current. When a user touches the screen,the two layers make contact in the contacted location, whereby a changein electrical field is noted and the coordinates of the contactedlocation calculated. In a capacitive touch screen, a capacitive layerstores electrical charge, which is discharged to the user upon contactwith the touch screen, causing a decrease in the charge of thecapacitive layer. The decrease is measured, and the contacted locationcoordinates determined. In a surface acoustic wave touch screen, anacoustic wave is transmitted through the screen, and the acoustic waveis disturbed by user contact. A receiving transducer detects the usercontact instance and determines the contacted location coordinates.

The term “display” refers to a portion of one or more screens used todisplay the output of a computer to a user. A display may be asingle-screen display or a multi-screen display, referred to as acomposite display. A composite display can encompass the touch sensitivedisplay of one or more screens. A single physical screen can includemultiple displays that are managed as separate logical displays. Thus,different content can be displayed on the separate displays althoughpart of the same physical screen.

The term “displayed image” refers to an image produced on the display. Atypical displayed image is a window or desktop. The displayed image mayoccupy all or a portion of the display.

The term “display orientation” refers to the way in which a rectangulardisplay is oriented by a user for viewing. The two most common types ofdisplay orientation are portrait and landscape. In landscape mode, thedisplay is oriented such that the width of the display is greater thanthe height of the display (such as a 4:3 ratio, which is 4 units wideand 3 units tall, or a 16:9 ratio, which is 16 units wide and 9 unitstall). Stated differently, the longer dimension of the display isoriented substantially horizontal in landscape mode while the shorterdimension of the display is oriented substantially vertical. In theportrait mode, by contrast, the display is oriented such that the widthof the display is less than the height of the display. Stateddifferently, the shorter dimension of the display is orientedsubstantially horizontal in the portrait mode while the longer dimensionof the display is oriented substantially vertical.

The term “composite display” refers to a logical structure that definesa display that can encompass one or more screens. A multi-screen displaycan be associated with a composite display that encompasses all thescreens. The composite display can have different displaycharacteristics based on the various orientations of the device.

The term “gesture” refers to a user action that expresses an intendedidea, action, meaning, result, and/or outcome. The user action caninclude manipulating a device (e.g., opening or closing a device,changing a device orientation, moving a trackball or wheel, etc.),movement of a body part in relation to the device, movement of animplement or tool in relation to the device, audio inputs, etc. Agesture may be made on a device (such as on the screen) or with thedevice to interact with the device.

The term “module” as used herein refers to any known or later developedhardware, software, firmware, artificial intelligence, fuzzy logic, orcombination of hardware and software that is capable of performing thefunctionality associated with that element.

The term “gesture capture” refers to a sense or otherwise a detection ofan instance and/or type of user gesture. The gesture capture can occurin one or more areas of the screen, A gesture region can be on thedisplay, where it may be referred to as a touch sensitive display or offthe display where it may be referred to as a gesture capture area.

A “multi-screen application” or “multiple-display application” refers toan application that is capable of multiple modes. The multi-screenapplication mode can include, but is not limited to, a single screenmode (where the application is displayed on a single screen) or acomposite display mode (where the application is displayed on two ormore screens). A multi-screen application can have different layoutsoptimized for the mode. Thus, the multi-screen application can havedifferent layouts for a single screen or for a composite display thatcan encompass two or more screens. The different layouts may havedifferent screen/display dimensions and/or configurations on which theuser interfaces of the multi-screen applications can be rendered. Thedifferent layouts allow the application to optimize the application'suser interface for the type of display, e.g., single screen or multiplescreens. In single screen mode, the multi-screen application may presentone window pane of information. In a composite display mode, themulti-screen application may present multiple window panes ofinformation or may provide a larger and a richer presentation becausethere is more space for the display contents. The multi-screenapplications may be designed to adapt dynamically to changes in thedevice and the mode depending on which display (single or composite) thesystem assigns to the multi-screen application. In alternativeembodiments, the user can use a gesture to request the applicationtransition to a different mode, and, if a display is available for therequested mode, the device can allow the application to move to thatdisplay and transition modes.

A “single-screen application” refers to an application that is capableof single screen mode. Thus, the single-screen application can produceonly one window and may not be capable of different modes or differentdisplay dimensions. A single-screen application may not be capable ofthe several modes discussed with the multi-screen application.

The term “window” refers to a, typically rectangular, displayed image onat least part of a display that contains or provides content differentfrom the rest of the screen. The window may obscure the desktop.

The terms “determine”, “calculate” and “compute,” and variationsthereof, as used herein, are used interchangeably and include any typeof methodology, process, mathematical operation or technique.

It shall be understood that the term “means” as used herein shall begiven its broadest possible interpretation in accordance with 35 U.S.C.,Section 112, Paragraph 6. Accordingly, a claim incorporating the term“means” shall cover all structures, materials, or acts set forth herein,and all of the equivalents thereof. Further, the structures, materialsor acts and the equivalents thereof shall include all those described inthe summary of the invention, brief description of the drawings,detailed description, abstract, and claims themselves.

The preceding is a simplified summary of the disclosure to provide anunderstanding of some aspects of the disclosure. This summary is neitheran extensive nor exhaustive overview of the disclosure and its variousaspects, embodiments, and/or configurations. It is intended neither toidentify key or critical elements of the disclosure nor to delineate thescope of the disclosure but to present selected concepts of thedisclosure in a simplified form as an introduction to the more detaileddescription presented below. As will be appreciated, other aspects,embodiments, and/or configurations of the disclosure are possibleutilizing, alone or in combination, one or more of the features setforth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A includes a first view of an embodiment of a multi-screen userdevice;

FIG. 1B includes a second view of an embodiment of a multi-screen userdevice;

FIG. 1C includes a third view of an embodiment of a multi-screen userdevice;

FIG. 1D includes a fourth view of an embodiment of a multi-screen userdevice;

FIG. 1E includes a fifth view of an embodiment of a multi-screen userdevice;

FIG. 1F includes a sixth view of an embodiment of a multi-screen userdevice;

FIG. 1G includes a seventh view of an embodiment of a multi-screen userdevice;

FIG. 1H includes a eighth view of an embodiment of a multi-screen userdevice;

FIG. 1I includes a ninth view of an embodiment of a multi-screen userdevice;

FIG. 1J includes a tenth view of an embodiment of a multi-screen userdevice;

FIG. 2 is a block diagram of an embodiment of the hardware of thedevice;

FIG. 3A is a block diagram of an embodiment of the state model for thedevice based on the device's orientation and/or configuration;

FIG. 3B is a table of an embodiment of the state model for the devicebased on the device's orientation and/or configuration;

FIG. 4A is a first representation of an embodiment of user gesturereceived at a device;

FIG. 4B is a second representation of an embodiment of user gesturereceived at a device;

FIG. 4C is a third representation of an embodiment of user gesturereceived at a device;

FIG. 4D is a fourth representation of an embodiment of user gesturereceived at a device;

FIG. 4E is a fifth representation of an embodiment of user gesturereceived at a device;

FIG. 4F is a sixth representation of an embodiment of user gesturereceived at a device;

FIG. 4G is a seventh representation of an embodiment of user gesturereceived at a device;

FIG. 4H is a eighth representation of an embodiment of user gesturereceived at a device;

FIG. 5A is a block diagram of an embodiment of the device softwareand/or firmware;

FIG. 5B is a second block diagram of an embodiment of the devicesoftware and/or firmware;

FIG. 6A is a first representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6B is a second representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6C is a third representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6D is a fourth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6E is a fifth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6F is a sixth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6G is a seventh representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6H is a eighth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6I is a ninth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6J is a tenth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 7A is representation of a logical window stack;

FIG. 7B is another representation of an embodiment of a logical windowstack;

FIG. 7C is another representation of an embodiment of a logical windowstack;

FIG. 7D is another representation of an embodiment of a logical windowstack;

FIG. 7E is another representation of an embodiment of a logical windowstack;

FIG. 8 is block diagram of an embodiment of a logical data structure fora window stack;

FIG. 9 is a flow chart of an embodiment of a method for creating awindow stack;

FIG. 10 is a flow chart of an embodiment of a method for managing theexecution of an application;

FIG. 11 is a block diagram of an embodiment of the hardware of a unifiedsystem;

FIG. 12 is a block diagram of an embodiment of the hardware of acomputer system;

FIG. 13 is a representation of an embodiment of a unified desktop;

FIG. 14 is a representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 15 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 16 is a flow chart of an embodiment of a method for providingstatus indicators in a unified desktop;

FIG. 17 is a flow chart of an embodiment of a method for providingstatus indicators in a unified desktop;

FIG. 18 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 19 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 20 is a flow chart of an embodiment of a method for providing afreeform window in a unified desktop;

FIG. 21 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 22 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 23 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 24 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 25 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 26 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 27 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 28 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 29 is a representation of a state diagram of a user interface in asleep state presented in a unified desktop;

FIG. 30 is a flow chart of an embodiment of a method for providing acommon wake and unlock strategy for a unified desktop;

FIG. 31 is another representation of an embodiment of user interfacespresented before docking a device with a computer system to form aunified desktop;

FIG. 32 is another representation of an embodiment of a user interfacepresented in a unified desktop after docking;

FIG. 33 is another representation of an embodiment of a user interfacepresented in a unified desktop after docking;

FIG. 34 is a flow chart of an embodiment of a method for docking adevice with a computer system to form a unified desktop;

FIG. 35 is another representation of an embodiment of a user interfacepresented in a unified desktop before undocking;

FIG. 36 is another representation of an embodiment of user interfacespresented after undocking a device with a computer system to dismantle aunified desktop;

FIG. 37 is a flow chart of an embodiment of a method for undocking adevice with a computer system;

FIG. 38 is a representation of a rules diagram for different rules thatgovern the docking and undocking of a device and a computer system;

FIG. 39 is a block diagram of an embodiment of the computing environmentof a unified system;

FIG. 40 is a representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 41A is a block diagram of an embodiment of a user interface datastructure associated with the unified desktop;

FIG. 41B is another block diagram of another embodiment of a userinterface data structure associated with the unified desktop;

FIG. 42 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 43A is a block diagram of an embodiment of a user interface datastructure associated with the unified desktop;

FIG. 43B is another block diagram of another embodiment of a userinterface data structure associated with the unified desktop;

FIG. 44 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 45A is a block diagram of an embodiment of a user interface datastructure associated with the unified desktop;

FIG. 45B is another block diagram of another embodiment of a userinterface data structure associated with the unified desktop;

FIG. 46 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 47A is a block diagram of an embodiment of a user interface datastructure associated with the unified desktop;

FIG. 47B is another block diagram of another embodiment of a userinterface data structure associated with the unified desktop;

FIG. 48 is a flow chart of an embodiment of a method for managing theuser interface when docking a device with a computer system;

FIG. 49 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 50 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 51 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 52 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 53 is a block diagram of an embodiment of data structure associatedwindows previously displayed when the device was previously docked withthe computer system;

FIG. 54 is a flow chart of an embodiment of a method for managing windowstickiness;

FIG. 55A is another block diagram of another embodiment of modulesassociated with the device docked with the computer system;

FIG. 55B is another block diagram of another embodiment of modulesassociated with the computer system docked with the device;

FIG. 56 is a flow chart of an embodiment of a method for processingevents in the unified system;

FIG. 57 is another flow chart of another embodiment of a method forprocessing events in the unified system;

FIG. 58 is another flow chart of another embodiment of a method forprocessing events in the unified system;

FIG. 59 is a flow chart of an embodiment of a method for the deviceassuming the role of master in the unified system;

FIG. 60 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 61A is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 61B is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 61C is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 62 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 63 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 64 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 65 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 66A is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 66B is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 67 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 68 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 69 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 70 is a flow chart of an embodiment of a method for providing atriad control in the unified system;

FIG. 71 is a flow chart of an embodiment of a method for providing anapplication manager interface in the unified system;

FIG. 72 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 73 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 74 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 75 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 76 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 77 is a flow chart of an embodiment of a method for providing anapplication manager interface in the unified system;

FIG. 78 is another representation of an embodiment of a user interfacepresented in a unified desktop

FIG. 79 is a flow chart of an embodiment of a method for providing a bigbrother application in the unified system;

FIG. 80 is another representation of an embodiment of a user interfacepresented in a unified desktop

FIG. 81 is another representation of an embodiment of a user interfacepresented in a unified desktop;

FIG. 82 is a flow chart of an embodiment of a method for providing a bigbrother application in the unified system;

FIG. 83 is an embodiment of a data structure associated with a bigbrother application in a unified desktop.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a letter thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference label.

DETAILED DESCRIPTION

Presented herein are embodiments of a device. The device can be acommunications device, such as a cellular telephone, or other smartdevice. The device can include two screens that are oriented to provideseveral unique display configurations. Further, the device can receiveuser input in unique ways. The overall design and functionality of thedevice provides for an enhanced user experience making the device moreuseful and more efficient.

Mechanical Features:

FIGS. 1A-1J illustrate a device 100 in accordance with embodiments ofthe present disclosure. As described in greater detail below, device 100can be positioned in a number of different ways each of which providesdifferent functionality to a user. The device 100 is a multi-screendevice that includes a primary screen 104 and a secondary screen 108,both of which are touch sensitive. In embodiments, the entire frontsurface of screens 104 and 108 may be touch sensitive and capable ofreceiving input by a user touching the front surface of the screens 104and 108. Primary screen 104 includes touch sensitive display 110, which,in addition to being touch sensitive, also displays information to auser. Secondary screen 108 includes touch sensitive display 114, whichalso displays information to a user. In other embodiments, screens 104and 108 may include more than one display area.

Primary screen 104 also includes a configurable area 112 that has beenconfigured for specific inputs when the user touches portions of theconfigurable area 112. Secondary screen 108 also includes a configurablearea 116 that has been configured for specific inputs. Areas 112 a and116 a have been configured to receive a “back” input indicating that auser would like to view information previously displayed. Areas 112 band 116 b have been configured to receive a “menu” input indicating thatthe user would like to view options from a menu. Areas 112 c and 116 chave been configured to receive a “home” input indicating that the userwould like to view information associated with a “home” view. In otherembodiments, areas 112 a-c and 116 a-c may be configured, in addition tothe configurations described above, for other types of specific inputsincluding controlling features of device 100, some non-limiting examplesincluding adjusting overall system power, adjusting the volume,adjusting the brightness, adjusting the vibration, selecting ofdisplayed items (on either of screen 104 or 108), operating a camera,operating a microphone, and initiating/terminating of telephone calls.Also, in some embodiments, areas 112 a-c and 116 a-c may be configuredfor specific inputs depending upon the application running on device 100and/or information displayed on touch sensitive displays 110 and/or 114.

In addition to touch sensing, primary screen 104 and secondary screen108 may also include areas that receive input from a user withoutrequiring the user to touch the display area of the screen. For example,primary screen 104 includes gesture capture area 120, and secondaryscreen 108 includes gesture capture area 124. These areas are able toreceive input by recognizing gestures made by a user without the needfor the user to actually touch the surface of the display area. Incomparison to touch sensitive displays 110 and 114, the gesture captureareas 120 and 124 are commonly not capable of rendering a displayedimage.

The two screens 104 and 108 are connected together with a hinge 128,shown clearly in FIG. 1C (illustrating a back view of device 100). Hinge128, in the embodiment shown in FIGS. 1A-1J, is a center hinge thatconnects screens 104 and 108 so that when the hinge is closed, screens104 and 108 are juxtaposed (i.e., side-by-side) as shown in FIG. 1B(illustrating a front view of device 100). Hinge 128 can be opened toposition the two screens 104 and 108 in different relative positions toeach other. As described in greater detail below, the device 100 mayhave different functionalities depending on the relative positions ofscreens 104 and 108.

FIG. 1D illustrates the right side of device 100. As shown in FIG. 1D,secondary screen 108 also includes a card slot 132 and a port 136 on itsside. Card slot 132 in embodiments, accommodates different types ofcards including a subscriber identity module (SIM). Port 136 inembodiments is an input/output port (I/O port) that allows device 100 tobe connected to other peripheral devices, such as a display, keyboard,or printing device. As can be appreciated, these are merely someexamples and in other embodiments device 100 may include other slots andports such as slots and ports for accommodating additional memorydevices and/or for connecting other peripheral devices. Also shown inFIG. 1D is an audio jack 140 that accommodates a tip, ring, sleeve (TRS)connector for example to allow a user to utilize headphones or aheadset.

Device 100 also includes a number of buttons 158. For example, FIG. 1Eillustrates the left side of device 100. As shown in FIG. 1E, the sideof primary screen 104 includes three buttons 144, 148, and 152, whichcan be configured for specific inputs. For example, buttons 144, 148,and 152 may be configured to, in combination or alone, control a numberof aspects of device 100. Some non-limiting examples include overallsystem power, volume, brightness, vibration, selection of displayeditems (on either of screen 104 or 108), a camera, a microphone, andinitiation/termination of telephone calls. In some embodiments, insteadof separate buttons two buttons may be combined into a rocker button.This arrangement is useful in situations where the buttons areconfigured to control features such as volume or brightness. In additionto buttons 144, 148, and 152, device 100 also includes a button 156,shown in FIG. 1F, which illustrates the top of device 100. In oneembodiment, button 156 is configured as an on/off button used to controloverall system power to device 100. In other embodiments, button 156 isconfigured to, in addition to or in lieu of controlling system power,control other aspects of device 100. In some embodiments, one or more ofthe buttons 144, 148, 152, and 156 are capable of supporting differentuser commands. By way of example, a normal press has a duration commonlyof less than about 1 second and resembles a quick tap. A medium presshas a duration commonly of 1 second or more but less than about 12seconds. A long press has a duration commonly of about 12 seconds ormore. The function of the buttons is normally specific to theapplication that is currently in focus on the respective display 110 and114. In a telephone application for instance and depending on theparticular button, a normal, medium, or long press can mean end call,increase in call volume, decrease in call volume, and toggle microphonemute. In a camera or video application for instance and depending on theparticular button, a normal, medium, or long press can mean increasezoom, decrease zoom, and take photograph or record video.

There are also a number of hardware components within device 100. Asillustrated in FIG. 1C, device 100 includes a speaker 160 and amicrophone 164. Device 100 also includes a camera 168 (FIG. 1B).Additionally, device 100 includes two position sensors 172A and 172B,which are used to determine the relative positions of screens 104 and108. In one embodiment, position sensors 172A and 172B are Hall effectsensors. However, in other embodiments other sensors can be used inaddition to or in lieu of the Hall effect sensors. An accelerometer 176may also be included as part of device 100 to determine the orientationof the device 100 and/or the orientation of screens 104 and 108.Additional internal hardware components that may be included in device100 are described below with respect to FIG. 2.

The overall design of device 100 allows it to provide additionalfunctionality not available in other communication devices. Some of thefunctionality is based on the various positions and orientations thatdevice 100 can have. As shown in FIGS. 1B-1G, device 100 can be operatedin an “open” position where screens 104 and 108 are juxtaposed. Thisposition allows a large display area for displaying information to auser. When position sensors 172A and 172B determine that device 100 isin the open position, they can generate a signal that can be used totrigger different events such as displaying information on both screens104 and 108. Additional events may be triggered if accelerometer 176determines that device 100 is in a portrait position (FIG. 1B) asopposed to a landscape position (not shown).

In addition to the open position, device 100 may also have a “closed”position illustrated in FIG. 1H. Again, position sensors 172A and 172Bcan generate a signal indicating that device 100 is in the “closed”position. This can trigger an event that results in a change ofdisplayed information on screen 104 and/or 108. For example, device 100may be programmed to stop displaying information on one of the screens,e.g., screen 108, since a user can only view one screen at a time whendevice 100 is in the “closed” position. In other embodiments, the signalgenerated by position sensors 172A and 172B, indicating that the device100 is in the “closed” position, can trigger device 100 to answer anincoming telephone call. The “closed” position can also be a preferredposition for utilizing the device 100 as a mobile phone.

Device 100 can also be used in an “easel” position which is illustratedin FIG. 1I. In the “easel” position, screens 104 and 108 are angled withrespect to each other and facing outward with the edges of screens 104and 108 substantially horizontal. In this position, device 100 can beconfigured to display information on both screens 104 and 108 to allowtwo users to simultaneously interact with device 100. When device 100 isin the “easel” position, sensors 172A and 172B generate a signalindicating that the screens 104 and 108 are positioned at an angle toeach other, and the accelerometer 176 can generate a signal indicatingthat device 100 has been placed so that the edge of screens 104 and 108are substantially horizontal. The signals can then be used incombination to generate events that trigger changes in the display ofinformation on screens 104 and 108.

FIG. 1J illustrates device 100 in a “modified easel” position. In the“modified easel” position, one of screens 104 or 108 is used as a standand is faced down on the surface of an object such as a table. Thisposition provides a convenient way for information to be displayed to auser in landscape orientation. Similar to the easel position, whendevice 100 is in the “modified easel” position, position sensors 172Aand 172B generate a signal indicating that the screens 104 and 108 arepositioned at an angle to each other. The accelerometer 176 wouldgenerate a signal indicating that device 100 has been positioned so thatone of screens 104 and 108 is faced downwardly and is substantiallyhorizontal. The signals can then be used to generate events that triggerchanges in the display of information of screens 104 and 108. Forexample, information may not be displayed on the screen that is facedown since a user cannot see the screen.

Transitional states are also possible. When the position sensors 172Aand B and/or accelerometer indicate that the screens are being closed orfolded (from open), a closing transitional state is recognized.Conversely when the position sensors 172A and B indicate that thescreens are being opened or folded (from closed), an openingtransitional state is recognized. The closing and opening transitionalstates are typically time-based, or have a maximum time duration from asensed starting point. Normally, no user input is possible when one ofthe closing and opening states is in effect. In this manner, incidentaluser contact with a screen during the closing or opening function is notmisinterpreted as user input. In embodiments, another transitional stateis possible when the device 100 is closed. This additional transitionalstate allows the display to switch from one screen 104 to the secondscreen 108 when the device 100 is closed based on some user input, e.g.,a double tap on the screen 110,114.

As can be appreciated, the description of device 100 is made forillustrative purposes only, and the embodiments are not limited to thespecific mechanical features shown in FIGS. 1A-1J and described above.In other embodiments, device 100 may include additional features,including one or more additional buttons, slots, display areas, hinges,and/or locking mechanisms. Additionally, in embodiments, the featuresdescribed above may be located in different parts of device 100 andstill provide similar functionality. Therefore, FIGS. 1A-1J and thedescription provided above are nonlimiting.

Hardware Features:

FIG. 2 illustrates components of a device 100 in accordance withembodiments of the present disclosure. In general, the device 100includes a primary screen 104 and a secondary screen 108. While theprimary screen 104 and its components are normally enabled in both theopened and closed positions or states, the secondary screen 108 and itscomponents are normally enabled in the opened state but disabled in theclosed state. However, even when in the closed state a user orapplication triggered interrupt (such as in response to a phoneapplication or camera application operation) can flip the active screen,or disable the primary screen 104 and enable the secondary screen 108,by a suitable command. Each screen 104, 108 can be touch sensitive andcan include different operative areas. For example, a first operativearea, within each touch sensitive screen 104 and 108, may comprise atouch sensitive display 110, 114. In general, the touch sensitivedisplay 110, 114 may comprise a full color, touch sensitive display. Asecond area within each touch sensitive screen 104 and 108 may comprisea gesture capture region 120, 124. The gesture capture region 120, 124may comprise an area or region that is outside of the touch sensitivedisplay 110, 114 area, and that is capable of receiving input, forexample in the form of gestures provided by a user. However, the gesturecapture region 120, 124 does not include pixels that can perform adisplay function or capability.

A third region of the touch sensitive screens 104 and 108 may comprise aconfigurable area 112, 116. The configurable area 112, 116 is capable ofreceiving input and has display or limited display capabilities. Inembodiments, the configurable area 112, 116 may present different inputoptions to the user. For example, the configurable area 112, 116 maydisplay buttons or other relatable items. Moreover, the identity ofdisplayed buttons, or whether any buttons are displayed at all withinthe configurable area 112, 116 of a touch sensitive screen 104 or 108,may be determined from the context in which the device 100 is usedand/or operated. In an exemplary embodiment, the touch sensitive screens104 and 108 comprise liquid crystal display devices extending across atleast those regions of the touch sensitive screens 104 and 108 that arecapable of providing visual output to a user, and a capacitive inputmatrix over those regions of the touch sensitive screens 104 and 108that are capable of receiving input from the user.

One or more display controllers 216 a, 216 b may be provided forcontrolling the operation of the touch sensitive screens 104 and 108,including input (touch sensing) and output (display) functions. In theexemplary embodiment illustrated in FIG. 2, a separate touch screencontroller 216 a or 216 b is provided for each touch screen 104 and 108.In accordance with alternate embodiments, a common or shared touchscreen controller may be used to control each of the included touchsensitive screens 104 and 108. In accordance with still otherembodiments, the functions of a touch screen controller may beincorporated into other components, such as a processor 204.

The processor 204 may comprise a general purpose programmable processoror controller for executing application programming or instructions. Inaccordance with at least some embodiments, the processor 204 may includemultiple processor cores, and/or implement multiple virtual processors.In accordance with still other embodiments, the processor 204 mayinclude multiple physical processors. As a particular example, theprocessor 204 may comprise a specially configured application specificintegrated circuit (ASIC) or other integrated circuit, a digital signalprocessor, a controller, a hardwired electronic or logic circuit, aprogrammable logic device or gate array, a special purpose computer, orthe like. The processor 204 generally functions to run programming codeor instructions implementing various functions of the device 100.

A communication device 100 may also include memory 208 for use inconnection with the execution of application programming or instructionsby the processor 204, and for the temporary or long term storage ofprogram instructions and/or data. As examples, the memory 208 maycomprise RAM, DRAM, SDRAM, or other solid state memory. Alternatively orin addition, data storage 212 may be provided. Like the memory 208, thedata storage 212 may comprise a solid state memory device or devices.Alternatively or in addition, the data storage 212 may comprise a harddisk drive or other random access memory.

In support of communications functions or capabilities, the device 100can include a cellular telephony module 228. As examples, the cellulartelephony module 228 can comprise a GSM, CDMA, FDMA and/or analogcellular telephony transceiver capable of supporting voice, multimediaand/or data transfers over a cellular network. Alternatively or inaddition, the device 100 can include an additional or other wirelesscommunications module 232. As examples, the other wirelesscommunications module 232 can comprise a wireless fidelity, BLUETOOTH™,WIMAX, infrared, or other wireless communications link. The cellulartelephony module 228 and the other wireless communications module 232can each be associated with a shared or a dedicated antenna 224.

A port interface 252 may be included. The port interface 252 may includeproprietary or universal ports to support the interconnection of thedevice 100 to other devices or components, such as a dock, which may ormay not include additional or different capabilities from those integralto the device 100. In addition to supporting an exchange ofcommunication signals between the device 100 and another device orcomponent, the docking port 136 and/or port interface 252 can supportthe supply of power to or from the device 100. The port interface 252also comprises an intelligent element that comprises a docking modulefor controlling communications or other interactions between the device100 and a connected device or component.

An input/output module 248 and associated ports may be included tosupport communications over wired networks or links, for example withother communication devices, server devices, and/or peripheral devices.Examples of an input/output module 248 include an Ethernet port, aUniversal Serial Bus (USB) port, Institute of Electrical and ElectronicsEngineers (IEEE) 1394, or other interface.

An audio input/output interface/device(s) 244 can be included to provideanalog audio to an interconnected speaker or other device, and toreceive analog audio input from a connected microphone or other device.As an example, the audio input/output interface/device(s) 244 maycomprise an associated amplifier and analog to digital converter.Alternatively or in addition, the device 100 can include an integratedaudio input/output device 256 and/or an audio jack for interconnectingan external speaker or microphone. For example, an integrated speakerand an integrated microphone can be provided, to support near talk orspeaker phone operations.

Hardware buttons 158 can be included for example for use in connectionwith certain control operations. Examples include a master power switch,volume control, etc., as described in conjunction with FIGS. 1A through1J. One or more image capture interfaces/devices 240, such as a camera,can be included for capturing still and/or video images. Alternativelyor in addition, an image capture interface/device 240 can include ascanner or code reader. An image capture interface/device 240 caninclude or be associated with additional elements, such as a flash orother light source.

The device 100 can also include a global positioning system (GPS)receiver 236. In accordance with embodiments of the present invention,the GPS receiver 236 may further comprise a GPS module that is capableof providing absolute location information to other components of thedevice 100. An accelerometer(s) 176 may also be included. For example,in connection with the display of information to a user and/or otherfunctions, a signal from the accelerometer 176 can be used to determinean orientation and/or format in which to display that information to theuser.

Embodiments of the present invention can also include one or moreposition sensor(s) 172. The position sensor 172 can provide a signalindicating the position of the touch sensitive screens 104 and 108relative to one another. This information can be provided as an input,for example to a user interface application, to determine an operatingmode, characteristics of the touch sensitive displays 110, 114, and/orother device 100 operations. As examples, a screen position sensor 172can comprise a series of Hall effect sensors, a multiple positionswitch, an optical switch, a Wheatstone bridge, a potentiometer, orother arrangement capable of providing a signal indicating which ofmultiple relative positions the touch screens are in.

Communications between various components of the device 100 can becarried by one or more buses 222. In addition, power can be supplied tothe components of the device 100 from a power source and/or powercontrol module 260. The power control module 260 can, for example,include a battery, an AC to DC converter, power control logic, and/orports for interconnecting the device 100 to an external source of power.

Device State:

FIGS. 3A and 3B represent illustrative states of device 100. While anumber of illustrative states are shown, and transitions from a firststate to a second state, it is to be appreciated that the illustrativestate diagram may not encompass all possible states and/or all possibletransitions from a first state to a second state. As illustrated in FIG.3, the various arrows between the states (illustrated by the staterepresented in the circle) represent a physical change that occurs tothe device 100, that is detected by one or more of hardware andsoftware, the detection triggering one or more of a hardware and/orsoftware interrupt that is used to control and/or manage one or morefunctions of device 100.

As illustrated in FIG. 3A, there are twelve exemplary “physical” states:closed 304, transition 308 (or opening transitional state), easel 312,modified easel 316, open 320, inbound/outbound call or communication324, image/video capture 328, transition 332 (or closing transitionalstate), landscape 340, docked 336, docked 344 and landscape 348. Next toeach illustrative state is a representation of the physical state of thedevice 100 with the exception of states 324 and 328, where the state isgenerally symbolized by the international icon for a telephone and theicon for a camera, respectively.

In state 304, the device is in a closed state with the device 100generally oriented in the portrait direction with the primary screen 104and the secondary screen 108 back-to-back in different planes (see FIG.1H). From the closed state, the device 100 can enter, for example,docked state 336, where the device 100 is coupled with a dockingstation, docking cable, or in general docked or associated with one ormore other devices or peripherals, or the landscape state 340, where thedevice 100 is generally oriented with the primary screen 104 facing theuser, and the primary screen 104 and the secondary screen 108 beingback-to-back.

In the closed state, the device can also move to a transitional statewhere the device remains closed but the display is moved from one screen104 to another screen 108 based on a user input, e.g., a double tap onthe screen 110, 114. Still another embodiment includes a bilateralstate. In the bilateral state, the device remains closed, but a singleapplication displays at least one window on both the first display 110and the second display 114. The windows shown on the first and seconddisplay 110, 114 may be the same or different based on the applicationand the state of that application. For example, while acquiring an imagewith a camera, the device may display the view finder on the firstdisplay 110 and displays a preview for the photo subjects (full screenand mirrored left-to-right) on the second display 114.

In state 308, a transition state from the closed state 304 to thesemi-open state or easel state 312, the device 100 is shown opening withthe primary screen 104 and the secondary screen 108 being rotated arounda point of axis coincident with the hinge. Upon entering the easel state312, the primary screen 104 and the secondary screen 108 are separatedfrom one another such that, for example, the device 100 can sit in aneasel-like configuration on a surface.

In state 316, known as the modified easel position, the device 100 hasthe primary screen 104 and the secondary screen 108 in a similarrelative relationship to one another as in the easel state 312, with thedifference being one of the primary screen 104 or the secondary screen108 is placed on a surface as shown.

State 320 is the open state where the primary screen 104 and thesecondary screen 108 are generally on the same plane. From the openstate, the device 100 can transition to the docked state 344 or the openlandscape state 348. In the open state 320, the primary screen 104 andthe secondary screen 108 are generally in the portrait-like orientationwhile in landscaped state 348 the primary screen 104 and the secondaryscreen 108 are generally in a landscape-like orientation.

State 324 is illustrative of a communication state, such as when aninbound or outbound call is being received or placed, respectively, bythe device 100. While not illustrated for clarity, it should beappreciated the device 100 can transition to the inbound/outbound callstate 324 from any state illustrated in FIG. 3. In a similar manner, theimage/video capture state 328 can be entered into from any other statein FIG. 3, with the image/video capture state 328 allowing the device100 to take one or more images via a camera and/or videos with a videocapture device 240.

Transition state 332 illustratively shows primary screen 104 and thesecondary screen 108 being closed upon one another for entry into, forexample, the closed state 304.

FIG. 3B illustrates, with reference to the key, the inputs that arereceived to detect a transition from a first state to a second state. InFIG. 3B, various combinations of states are shown with in general, aportion of the columns being directed toward a portrait state 352, alandscape state 356, and a portion of the rows being directed toportrait state 360 and landscape state 364.

In FIG. 3B, the Key indicates that “H” represents an input from one ormore Hall Effect sensors, “A” represents an input from one or moreaccelerometers, “T” represents an input from a timer, “P” represents acommunications trigger input and “I” represents an image and/or videocapture request input. Thus, in the center portion 376 of the chart, aninput, or combination of inputs, are shown that represent how the device100 detects a transition from a first physical state to a secondphysical state.

As discussed, in the center portion of the chart 376, the inputs thatare received enable the detection of a transition from, for example, aportrait open state to a landscape easel state—shown in bold—“HAT.” Forthis exemplary transition from the portrait open to the landscape easelstate, a Hall Effect sensor (“H”), an accelerometer (“A”) and a timer(“T”) input may be needed. The timer input can be derived from, forexample, a clock associated with the processor.

In addition to the portrait and landscape states, a docked state 368 isalso shown that is triggered based on the receipt of a docking signal372. As discussed above and in relation to FIG. 3, the docking signalcan be triggered by the association of the device 100 with one or moreother device 100 s, accessories, peripherals, smart docks, or the like.

User Interaction:

FIGS. 4A through 4H depict various graphical representations of gestureinputs that may be recognized by the screens 104, 108. The gestures maybe performed not only by a user's body part, such as a digit, but alsoby other devices, such as a stylus, that may be sensed by the contactsensing portion(s) of a screen 104, 108. In general, gestures areinterpreted differently, based on where the gestures are performed(either directly on the display 110, 114 or in the gesture captureregion 120, 124). For example, gestures in the display 110,114 may bedirected to a desktop or application, and gestures in the gesturecapture region 120, 124 may be interpreted as for the system.

With reference to FIGS. 4A-4H, a first type of gesture, a touch gesture420, is substantially stationary on the screen 104,108 for a selectedlength of time. A circle 428 represents a touch or other contact typereceived at particular location of a contact sensing portion of thescreen. The circle 428 may include a border 432, the thickness of whichindicates a length of time that the contact is held substantiallystationary at the contact location. For instance, a tap 420 (or shortpress) has a thinner border 432 a than the border 432 b for a long press424 (or for a normal press). The long press 424 may involve a contactthat remains substantially stationary on the screen for longer timeperiod than that of a tap 420. As will be appreciated, differentlydefined gestures may be registered depending upon the length of timethat the touch remains stationary prior to contact cessation or movementon the screen.

With reference to FIG. 4C, a drag gesture 400 on the screen 104,108 isan initial contact (represented by circle 428) with contact movement 436in a selected direction. The initial contact 428 may remain stationaryon the screen 104,108 for a certain amount of time represented by theborder 432. The drag gesture typically requires the user to contact anicon, window, or other displayed image at a first location followed bymovement of the contact in a drag direction to a new second locationdesired for the selected displayed image. The contact movement need notbe in a straight line but have any path of movement so long as thecontact is substantially continuous from the first to the secondlocations.

With reference to FIG. 4D, a flick gesture 404 on the screen 104,108 isan initial contact (represented by circle 428) with truncated contactmovement 436 (relative to a drag gesture) in a selected direction. Inembodiments, a flick has a higher exit velocity for the last movement inthe gesture compared to the drag gesture. The flick gesture can, forinstance, be a finger snap following initial contact. Compared to a draggesture, a flick gesture generally does not require continual contactwith the screen 104,108 from the first location of a displayed image toa predetermined second location. The contacted displayed image is movedby the flick gesture in the direction of the flick gesture to thepredetermined second location. Although both gestures commonly can movea displayed image from a first location to a second location, thetemporal duration and distance of travel of the contact on the screen isgenerally less for a flick than for a drag gesture.

With reference to FIG. 4E, a pinch gesture 408 on the screen 104,108 isdepicted. The pinch gesture 408 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104 or 108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in opposing directions. Stated anotherway, the first contact movement 436 a is towards the second contact 436b, and the second contact movement 436 b is towards the first contact436 a. More simply stated, the pinch gesture 408 may be accomplished bya user's digits touching the screen 104,108 in a pinching motion.

With reference to FIG. 4F, a spread gesture 410 on the screen 104,108 isdepicted. The spread gesture 410 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104,108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in a common direction. Stated anotherway, the first and second contact movements 436 a, b are away from thefirst and second contacts 428 a, b. More simply stated, the spreadgesture 410 may be accomplished by a user's digits touching the screen104,108 in a spreading motion.

The above gestures may be combined in any manner, such as those shown byFIGS. 4G and 4H, to produce a determined functional result. For example,in FIG. 4G a tap gesture 420 is combined with a drag or flick gesture412 in a direction away from the tap gesture 420. In FIG. 4H, a tapgesture 420 is combined with a drag or flick gesture 412 in a directiontowards the tap gesture 420.

The functional result of receiving a gesture can vary depending on anumber of factors, including a state of the device 100, display 110,114, or screen 104, 108, a context associated with the gesture, orsensed location of the gesture. The state of the device commonly refersto one or more of a configuration of the device 100, a displayorientation, and user and other inputs received by the device 100.Context commonly refers to one or more of the particular application(s)selected by the gesture and the portion(s) of the application currentlyexecuting, whether the application is a single- or multi-screenapplication, and whether the application is a multi-screen applicationdisplaying one or more windows in one or more screens or in one or morestacks. Sensed location of the gesture commonly refers to whether thesensed set(s) of gesture location coordinates are on a touch sensitivedisplay 110, 114 or a gesture capture region 120, 124, whether thesensed set(s) of gesture location coordinates are associated with acommon or different display or screen 104,108, and/or what portion ofthe gesture capture region contains the sensed set(s) of gesturelocation coordinates.

A tap, when received by an a touch sensitive display 110, 114, can beused, for instance, to select an icon to initiate or terminate executionof a corresponding application, to maximize or minimize a window, toreorder windows in a stack, and to provide user input such as bykeyboard display or other displayed image. A drag, when received by atouch sensitive display 110, 114, can be used, for instance, to relocatean icon or window to a desired location within a display, to reorder astack on a display, or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). A flick, whenreceived by a touch sensitive display 110, 114 or a gesture captureregion 120, 124, can be used to relocate a window from a first displayto a second display or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). Unlike thedrag gesture, however, the flick gesture is generally not used to movethe displayed image to a specific user-selected location but to adefault location that is not configurable by the user.

The pinch gesture, when received by a touch sensitive display 110, 114or a gesture capture region 120, 124, can be used to minimize orotherwise increase the displayed area or size of a window (typicallywhen received entirely by a common display), to switch windows displayedat the top of the stack on each display to the top of the stack of theother display (typically when received by different displays orscreens), or to display an application manager (a “pop-up window” thatdisplays the windows in the stack). The spread gesture, when received bya touch sensitive display 110, 114 or a gesture capture region 120, 124,can be used to maximize or otherwise decrease the displayed area or sizeof a window, to switch windows displayed at the top of the stack on eachdisplay to the top of the stack of the other display (typically whenreceived by different displays or screens), or to display an applicationmanager (typically when received by an off-screen gesture capture regionon the same or different screens).

The combined gestures of FIG. 4G, when received by a common displaycapture region in a common display or screen 104,108, can be used tohold a first window stack location in a first stack constant for adisplay receiving the gesture while reordering a second window stacklocation in a second window stack to include a window in the displayreceiving the gesture. The combined gestures of FIG. 4H, when receivedby different display capture regions in a common display or screen104,108 or in different displays or screens, can be used to hold a firstwindow stack location in a first window stack constant for a displayreceiving the tap part of the gesture while reordering a second windowstack location in a second window stack to include a window in thedisplay receiving the flick or drag gesture. Although specific gesturesand gesture capture regions in the preceding examples have beenassociated with corresponding sets of functional results, it is to beappreciated that these associations can be redefined in any manner toproduce differing associations between gestures and/or gesture captureregions and/or functional results.

Firmware and Software:

The memory 508 may store and the processor 504 may execute one or moresoftware components. These components can include at least one operatingsystem (OS) 516, an application manager 562, a desktop 566, and/or oneor more applications 564 a and/or 564 b from an application store 560.The OS 516 can include a framework 520, one or more frame buffers 548,one or more drivers 512, previously described in conjunction with FIG.2, and/or a kernel 518. The OS 516 can be any software, consisting ofprograms and data, which manages computer hardware resources andprovides common services for the execution of various applications 564.The OS 516 can be any operating system and, at least in someembodiments, dedicated to mobile devices, including, but not limited to,Linux, ANDROID™, IPHONE OS (IOS™), WINDOWS PHONE 7™, etc. The OS 516 isoperable to provide functionality to the phone by executing one or moreoperations, as described herein.

The applications 564 can be any higher level software that executesparticular functionality for the user. Applications 564 can includeprograms such as email clients, web browsers, texting applications,games, media players, office suites, etc. The applications 564 can bestored in an application store 560, which may represent any memory ordata storage, and the management software associated therewith, forstoring the applications 564. Once executed, the applications 564 may berun in a different area of memory 508.

The framework 520 may be any software or data that allows the multipletasks running on the device to interact. In embodiments, at leastportions of the framework 520 and the discrete components describedhereinafter may be considered part of the OS 516 or an application 564.However, these portions will be described as part of the framework 520,but those components are not so limited. The framework 520 can include,but is not limited to, a Multi-Display Management (MDM) module 524, aSurface Cache module 528, a Window Management module 532, an InputManagement module 536, a Task Management module 540, an ApplicationModel Manager 542, a Display Controller, one or more frame buffers 548,a task stack 552, one or more window stacks 550 (which is a logicalarrangement of windows and/or desktops in a display area), and/or anevent buffer 556.

The MDM module 524 includes one or more modules that are operable tomanage the display of applications or other data on the screens of thedevice. An embodiment of the MDM module 524 is described in conjunctionwith FIG. 5B. In embodiments, the MDM module 524 receives inputs fromthe other OS 516 components, such as, the drivers 512, and from theapplications 564 to determine continually the state of the device 100.The inputs assist the MDM module 524 in determining how to configure andallocate the displays according to the application's preferences andrequirements, and the user's actions. Once a determination for displayconfigurations is made, the MDM module 524 can bind the applications 564to a display. The configuration may then be provided to one or moreother components to generate a window with a display.

The Surface Cache module 528 includes any memory or storage and thesoftware associated therewith to store or cache one or more images ofwindows. A series of active and/or non-active windows (or other displayobjects, such as, a desktop display) can be associated with eachdisplay. An active window (or other display object) is currentlydisplayed. Non-active windows (or other display objects) were openedand, at some time, displayed but are now not displayed. To enhance theuser experience, before a window transitions from an active state to aninactive state, a “screen shot” of a last generated image of the window(or other display object) can be stored. The Surface Cache module 528may be operable to store a bitmap of the last active image of a window(or other display object) not currently displayed. Thus, the SurfaceCache module 528 stores the images of non-active windows (or otherdisplay objects) in a data store.

In embodiments, the Window Management module 532 is operable to managethe windows (or other display objects) that are active or not active oneach of the displays. The Window Management module 532, based oninformation from the MDM module 524, the OS 516, or other components,determines when a window (or other display object) is visible or notactive. The Window Management module 532 may then put a non-visiblewindow (or other display object) in a “not active state” and, inconjunction with the Task Management module Task Management 540 suspendsthe application's operation. Further, the Window Management module 532may assign, through collaborative interaction with the MDM module 524, adisplay identifier to the window (or other display object) or manage oneor more other items of data associated with the window (or other displayobject). The Window Management module 532 may also provide the storedinformation to the application 564, the Task Management module 540, orother components interacting with or associated with the window (orother display object). The Window Management module 532 can alsoassociate an input task with a window based on window focus and displaycoordinates within the motion space.

The Input Management module 536 is operable to manage events that occurwith the device. An event is any input into the window environment, forexample, a user interface interaction with a user. The Input Managementmodule 536 receives the events and logically stores the events in anevent buffer 556. Events can include such user interface interactions asa “down event,” which occurs when a screen 104, 108 receives a touchsignal from a user, a “move event,” which occurs when the screen 104,108 determines that a user's finger is moving across a screen(s), an “upevent, which occurs when the screen 104, 108 determines that the userhas stopped touching the screen 104, 108, etc. These events arereceived, stored, and forwarded to other modules by the Input Managementmodule 536. The Input Management module 536 may also map screen inputsto a motion space which is the culmination of all physical and virtualdisplay available on the device.

The motion space is a virtualized space that includes all touchsensitive displays 110,114 “tiled” together to mimic the physicaldimensions of the device 100. For example, when the device 100 isunfolded, the motion space size may be 960×800, which may be the numberof pixels in the combined display area for both touch sensitive displays110, 114. If a user touches on a first touch sensitive display 110 onlocation (40, 40), a full screen window can receive touch event withlocation (40, 40). If a user touches on a second touch sensitive display114, with location (40, 40), the full screen window can receive touchevent with location (520, 40), because the second touch sensitivedisplay 114 is on the right side of the first touch sensitive display110, so the device 100 can offset the touch by the first touch sensitivedisplay's 110 width, which is 480 pixels. When a hardware event occurswith location info from a driver 512, the framework 520 can up-scale thephysical location to the motion space because the location of the eventmay be different based on the device orientation and state. The motionspace may be as described in U.S. patent application Ser. No.13/187,026, filed Jul. 20, 2011, entitled “Systems and Methods forReceiving Gesture Inputs Spanning Multiple Input Devices,” which ishereby incorporated by reference in its entirety for all that it teachesand for all purposes.

A task can be an application and a sub-task can be an applicationcomponent that provides a window with which users can interact to dosomething, such as dial the phone, take a photo, send an email, or viewa map. Each task may be given a window in which to draw a userinterface. The window typically fills a display (for example, touchsensitive display 110,114), but may be smaller than the display 110,114and float on top of other windows. An application usually consists ofmultiple sub-tasks that are loosely bound to each other. Typically, onetask in an application is specified as the “main” task, which ispresented to the user when launching the application for the first time.Each task can then start another task or sub-task to perform differentactions.

The Task Management module 540 is operable to manage the operation ofone or more applications 564 that may be executed by the device. Thus,the Task Management module 540 can receive signals to launch, suspend,terminate, etc. an application or application sub-tasks stored in theapplication store 560. The Task Management module 540 may theninstantiate one or more tasks or sub-tasks of the application 564 tobegin operation of the application 564. Further, the Task ManagementModule 540 may launch, suspend, or terminate a task or sub-task as aresult of user input or as a result of a signal from a collaboratingframework 520 component. The Task Management Module 540 is responsiblefor managing the lifecycle of applications (tasks and sub-task) fromwhen the application is launched to when the application is terminated.

The processing of the Task Management Module 540 is facilitated by atask stack 552, which is a logical structure associated with the TaskManagement Module 540. The task stack 552 maintains the state of alltasks and sub-tasks on the device 100. When some component of theoperating system 516 requires a task or sub-task to transition in itslifecycle, the OS 516 component can notify the Task Management Module540. The Task Management Module 540 may then locate the task orsub-task, using identification information, in the task stack 552, andsend a signal to the task or sub-task indicating what kind of lifecycletransition the task needs to execute. Informing the task or sub-task ofthe transition allows the task or sub-task to prepare for the lifecyclestate transition. The Task Management Module 540 can then execute thestate transition for the task or sub-task. In embodiments, the statetransition may entail triggering the OS kernel 518 to terminate the taskwhen termination is required.

Further, the Task Management module 540 may suspend the application 564based on information from the Window Management Module 532. Suspendingthe application 564 may maintain application data in memory but maylimit or stop the application 564 from rendering a window or userinterface. Once the application becomes active again, the TaskManagement module 540 can again trigger the application to render itsuser interface. In embodiments, if a task is suspended, the task maysave the task's state in case the task is terminated. In the suspendedstate, the application task may not receive input because theapplication window is not visible to the user.

The frame buffer 548 is a logical structure(s) used to render the userinterface. The frame buffer 548 can be created and destroyed by the OSkernel 518. However, the Display Controller 544 can write the imagedata, for the visible windows, into the frame buffer 548. A frame buffer548 can be associated with one screen or multiple screens. Theassociation of a frame buffer 548 with a screen can be controlleddynamically by interaction with the OS kernel 518. A composite displaymay be created by associating multiple screens with a single framebuffer 548. Graphical data used to render an application's window userinterface may then be written to the single frame buffer 548, for thecomposite display, which is output to the multiple screens 104,108. TheDisplay Controller 544 can direct an application's user interface to aportion of the frame buffer 548 that is mapped to a particular display110,114, thus, displaying the user interface on only one screen 104 or108. The Display Controller 544 can extend the control over userinterfaces to multiple applications, controlling the user interfaces foras many displays as are associated with a frame buffer 548 or a portionthereof. This approach compensates for the multiple physical screens104,108 that are in use by the software component above the DisplayController 544.

The Application Manager 562 is an application that provides apresentation layer for the window environment. Thus, the ApplicationManager 562 provides the graphical model for rendering by the TaskManagement Module 540. Likewise, the Desktop 566 provides thepresentation layer for the Application Store 560. Thus, the desktopprovides a graphical model of a surface having selectable applicationicons for the Applications 564 in the Application Store 560 that can beprovided to the Window Management Module 556 for rendering.

Further, the framework can include an Application Model Manager (AMM)542. The Application Manager 562 may interface with the AMM 542. Inembodiments, the AMM 542 receives state change information from thedevice 100 regarding the state of applications (which are running orsuspended). The AMM 542 can associate bit map images from the SurfaceCache Module 528 to the tasks that are alive (running or suspended).Further, the AMM 542 can convert the logical window stack maintained inthe Task Manager Module 540 to a linear (“film strip” or “deck ofcards”) organization that the user perceives when the using the offgesture capture area 120 to sort through the windows. Further, the AMM542 may provide a list of executing applications to the ApplicationManager 562.

An embodiment of the MDM module 524 is shown in FIG. 5B. The MDM module524 is operable to determine the state of the environment for thedevice, including, but not limited to, the orientation of the device,whether the device 100 is opened or closed, what applications 564 areexecuting, how the applications 564 are to be displayed, what actionsthe user is conducting, the tasks being displayed, etc. To configure thedisplay, the MDM module 524 interprets these environmental factors anddetermines a display configuration, as described in conjunction withFIGS. 6A-6J. Then, the MDM module 524 can bind the applications 564 orother device components to the displays. The configuration may then besent to the Display Controller 544 and/or the other components withinthe OS 516 to generate the display. The MDM module 524 can include oneor more of, but is not limited to, a Display Configuration Module 568, aPreferences Module 572, a Device State Module 574, a Gesture Module 576,a Requirements Module 580, an Event Module 584, and/or a Binding Module588.

The Display Configuration Module 568 determines the layout for thedisplay. In embodiments, the Display Configuration Module 568 candetermine the environmental factors. The environmental factors may bereceived from one or more other MDM modules 524 or from other sources.The Display Configuration Module 568 can then determine from the list offactors the best configuration for the display. Some embodiments of thepossible configurations and the factors associated therewith aredescribed in conjunction with FIGS. 6A-6F.

The Preferences Module 572 is operable to determine display preferencesfor an application 564 or other component. For example, an applicationcan have a preference for Single or Dual displays. The PreferencesModule 572 can determine an application's display preference (e.g., byinspecting the application's preference settings) and may allow theapplication 564 to change to a mode (e.g., single screen, dual screen,max, etc.) if the device 100 is in a state that can accommodate thepreferred mode. However, some user interface policies may disallow amode even if the mode is available. As the configuration of the devicechanges, the preferences may be reviewed to determine if a betterdisplay configuration can be achieved for an application 564.

The Device State Module 574 is operable to determine or receive thestate of the device. The state of the device can be as described inconjunction with FIGS. 3A and 3B. The state of the device can be used bythe Display Configuration Module 568 to determine the configuration forthe display. As such, the Device State Module 574 may receive inputs andinterpret the state of the device. The state information is thenprovided to the Display Configuration Module 568.

The Gesture Module 576 is shown as part of the MDM module 524, but, inembodiments, the Gesture module 576 may be a separate Framework 520component that is separate from the MDM module 524. In embodiments, theGesture Module 576 is operable to determine if the user is conductingany actions on any part of the user interface. In alternativeembodiments, the Gesture Module 576 receives user interface actions fromthe configurable area 112,116 only. The Gesture Module 576 can receivetouch events that occur on the configurable area 112,116 (or possiblyother user interface areas) by way of the Input Management Module 536and may interpret the touch events (using direction, speed, distance,duration, and various other parameters) to determine what kind ofgesture the user is performing. When a gesture is interpreted, theGesture Module 576 can initiate the processing of the gesture and, bycollaborating with other Framework 520 components, can manage therequired window animation. The Gesture Module 576 collaborates with theApplication Model Manager 542 to collect state information with respectto which applications are running (active or paused) and the order inwhich applications must appear when a user gesture is performed. TheGesture Module 576 may also receive references to bitmaps (from theSurface Cache Module 528) and live windows so that when a gesture occursit can instruct the Display Controller 544 how to move the window(s)across the display 110,114. Thus, suspended applications may appear tobe running when those windows are moved across the display 110,114.

Further, the Gesture Module 576 can receive task information either fromthe Task Management Module 540 or the Input Management module 536. Thegestures may be as defined in conjunction with FIGS. 4A through 4H. Forexample, moving a window causes the display to render a series ofdisplay frames that illustrate the window moving. The gesture associatedwith such user interface interaction can be received and interpreted bythe Gesture Module 576. The information about the user gesture is thensent to the Task Management Module 540 to modify the display binding ofthe task.

The Requirements Module 580, similar to the Preferences Module 572, isoperable to determine display requirements for an application 564 orother component. An application can have a set display requirement thatmust be observed. Some applications require a particular displayorientation. For example, the application “ANGRY BIRDS” can only bedisplayed in landscape orientation. This type of display requirement canbe determined or received, by the Requirements Module 580. As theorientation of the device changes, the Requirements Module 580 canreassert the display requirements for the application 564. The DisplayConfiguration Module 568 can generate a display configuration that is inaccordance with the application display requirements, as provided by theRequirements Module 580.

The Event Module 584, similar to the Gesture Module 576, is operable todetermine one or more events occurring with an application or othercomponent that can affect the user interface. Thus, the Event Module 584can receive event information either from the event buffer 556 or theTask Management module 540. These events can change how the tasks arebound to the displays. The Event Module 584 can collect state changeinformation from other Framework 520 components and act upon that statechange information. In an example, when the phone is opened or closed orwhen an orientation change has occurred, a new message may be renderedin a secondary screen. The state change based on the event can bereceived and interpreted by the Event Module 584. The information aboutthe events then may be sent to the Display Configuration Module 568 tomodify the configuration of the display.

The Binding Module 588 is operable to bind the applications 564 or theother components to the configuration determined by the DisplayConfiguration Module 568. A binding associates, in memory, the displayconfiguration for each application with the display and mode of theapplication. Thus, the Binding Module 588 can associate an applicationwith a display configuration for the application (e.g. landscape,portrait, multi-screen, etc.). Then, the Binding Module 588 may assign adisplay identifier to the display. The display identifier associated theapplication with a particular display of the device 100. This binding isthen stored and provided to the Display Controller 544, the othercomponents of the OS 516, or other components to properly render thedisplay. The binding is dynamic and can change or be updated based onconfiguration changes associated with events, gestures, state changes,application preferences or requirements, etc.

User Interface Configurations:

With reference now to FIGS. 6A-J, various types of output configurationsmade possible by the device 100 will be described hereinafter.

FIGS. 6A and 6B depict two different output configurations of the device100 being in a first state. Specifically, FIG. 6A depicts the device 100being in a closed portrait state 304 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first portrait configuration 604.As can be appreciated, the first portrait configuration 604 may onlydisplay a desktop or operating system home screen. Alternatively, one ormore windows may be presented in a portrait orientation while the device100 is displaying data in the first portrait configuration 604.

FIG. 6B depicts the device 100 still being in the closed portrait state304, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second portrait configuration 608.

It may be possible to display similar or different data in either thefirst or second portrait configuration 604, 608. It may also be possibleto transition between the first portrait configuration 604 and secondportrait configuration 608 by providing the device 100 a user gesture(e.g., a double tap gesture), a menu selection, or other means. Othersuitable gestures may also be employed to transition betweenconfigurations. Furthermore, it may also be possible to transition thedevice 100 from the first or second portrait configuration 604, 608 toany other configuration described herein depending upon which state thedevice 100 is moved.

An alternative output configuration may be accommodated by the device100 being in a second state. Specifically, FIG. 6C depicts a thirdportrait configuration where data is displayed simultaneously on boththe primary screen 104 and the secondary screen 108. The third portraitconfiguration may be referred to as a Dual-Portrait (PD) outputconfiguration. In the PD output configuration, the touch sensitivedisplay 110 of the primary screen 104 depicts data in the first portraitconfiguration 604 while the touch sensitive display 114 of the secondaryscreen 108 depicts data in the second portrait configuration 608. Thesimultaneous presentation of the first portrait configuration 604 andthe second portrait configuration 608 may occur when the device 100 isin an open portrait state 320. In this configuration, the device 100 maydisplay one application window in one display 110 or 114, twoapplication windows (one in each display 110 and 114), one applicationwindow and one desktop, or one desktop. Other configurations may bepossible. It should be appreciated that it may also be possible totransition the device 100 from the simultaneous display ofconfigurations 604, 608 to any other configuration described hereindepending upon which state the device 100 is moved. Furthermore, whilein this state, an application's display preference may place the deviceinto bilateral mode, in which both displays are active to displaydifferent windows in the same application. For example, a Cameraapplication may display a viewfinder and controls on one side, while theother side displays a mirrored preview that can be seen by the photosubjects. Games involving simultaneous play by two players may also takeadvantage of bilateral mode.

FIGS. 6D and 6E depict two further output configurations of the device100 being in a third state. Specifically, FIG. 6D depicts the device 100being in a closed landscape state 340 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first landscape configuration 612.Much like the other configurations described herein, the first landscapeconfiguration 612 may display a desktop, a home screen, one or morewindows displaying application data, or the like.

FIG. 6E depicts the device 100 still being in the closed landscape state340, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second landscape configuration 616. It may be possible todisplay similar or different data in either the first or second portraitconfiguration 612, 616. It may also be possible to transition betweenthe first landscape configuration 612 and second landscape configuration616 by providing the device 100 with one or both of a twist and tapgesture or a flip and slide gesture. Other suitable gestures may also beemployed to transition between configurations. Furthermore, it may alsobe possible to transition the device 100 from the first or secondlandscape configuration 612, 616 to any other configuration describedherein depending upon which state the device 100 is moved.

FIG. 6F depicts a third landscape configuration where data is displayedsimultaneously on both the primary screen 104 and the secondary screen108. The third landscape configuration may be referred to as aDual-Landscape (LD) output configuration. In the LD outputconfiguration, the touch sensitive display 110 of the primary screen 104depicts data in the first landscape configuration 612 while the touchsensitive display 114 of the secondary screen 108 depicts data in thesecond landscape configuration 616. The simultaneous presentation of thefirst landscape configuration 612 and the second landscape configuration616 may occur when the device 100 is in an open landscape state 340. Itshould be appreciated that it may also be possible to transition thedevice 100 from the simultaneous display of configurations 612, 616 toany other configuration described herein depending upon which state thedevice 100 is moved.

FIGS. 6G and 6H depict two views of a device 100 being in yet anotherstate. Specifically, the device 100 is depicted as being in an easelstate 312. FIG. 6G shows that a first easel output configuration 618 maybe displayed on the touch sensitive display 110. FIG. 6H shows that asecond easel output configuration 620 may be displayed on the touchsensitive display 114. The device 100 may be configured to depict eitherthe first easel output configuration 618 or the second easel outputconfiguration 620 individually. Alternatively, both the easel outputconfigurations 618, 620 may be presented simultaneously. In someembodiments, the easel output configurations 618, 620 may be similar oridentical to the landscape output configurations 612, 616. The device100 may also be configured to display one or both of the easel outputconfigurations 618, 620 while in a modified easel state 316. It shouldbe appreciated that simultaneous utilization of the easel outputconfigurations 618, 620 may facilitate two-person games (e.g.,Battleship®, chess, checkers, etc.), multi-user conferences where two ormore users share the same device 100, and other applications. As can beappreciated, it may also be possible to transition the device 100 fromthe display of one or both configurations 618, 620 to any otherconfiguration described herein depending upon which state the device 100is moved.

FIG. 6I depicts yet another output configuration that may beaccommodated while the device 100 is in an open portrait state 320.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in aportrait configuration referred to herein as a Portrait-Max (PMax)configuration 624. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Pmaxconfiguration 624 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Pmax configuration 624 to any other outputconfiguration described herein depending upon which state the device 100is moved.

FIG. 6J depicts still another output configuration that may beaccommodated while the device 100 is in an open landscape state 348.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in alandscape configuration referred to herein as a Landscape-Max (LMax)configuration 628. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Lmaxconfiguration 628 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Lmax configuration 628 to any other outputconfiguration described herein depending upon which state the device 100is moved.

The device 100 manages desktops and/or windows with at least one windowstack 700, 728, as shown in FIGS. 7A and 7B. A window stack 700, 728 isa logical arrangement of active and/or inactive windows for amulti-screen device. For example, the window stack 700, 728 may belogically similar to a deck of cards, where one or more windows ordesktops are arranged in order, as shown in FIGS. 7A and 7B. An activewindow is a window that is currently being displayed on at least one ofthe touch sensitive displays 110, 114. For example, windows 104 and 108are active windows and are displayed on touch sensitive displays 110 and114. An inactive window is a window that was opened and displayed but isnow “behind” an active window and not being displayed. In embodiments,an inactive window may be for an application that is suspended, andthus, the window is not displaying active content. For example, windows712, 716, 720, and 724 are inactive windows.

A window stack 700, 728 may have various arrangements or organizationalstructures. In the embodiment shown in FIG. 7A, the device 100 includesa first stack 760 associated with a first touch sensitive display 110and a second stack associated with a second touch sensitive display 114.Thus, each touch sensitive display 110, 114 can have an associatedwindow stack 760, 764. These two window stacks 760, 764 may havedifferent numbers of windows arranged in the respective stacks 760, 764.Further, the two window stacks 760, 764 can also be identifieddifferently and managed separately. Thus, the first window stack 760 canbe arranged in order from a first window 704 to a next window 720 to alast window 724 and finally to a desktop 722, which, in embodiments, isat the “bottom” of the window stack 760. In embodiments, the desktop 722is not always at the “bottom” as application windows can be arranged inthe window stack below the desktop 722, and the desktop 722 can bebrought to the “top” of a stack over other windows during a desktopreveal. Likewise, the second stack 764 can be arranged from a firstwindow 708 to a next window 712 to a last window 716, and finally to adesktop 718, which, in embodiments, is a single desktop area, withdesktop 722, under all the windows in both window stack 760 and windowstack 764. A logical data structure for managing the two window stacks760, 764 may be as described in conjunction with FIG. 8.

Another arrangement for a window stack 728 is shown in FIG. 7B. In thisembodiment, there is a single window stack 728 for both touch sensitivedisplays 110, 114. Thus, the window stack 728 is arranged from a desktop758 to a first window 744 to a last window 756. A window can be arrangedin a position among all windows without an association to a specifictouch sensitive display 110, 114. In this embodiment, a window is in theorder of windows. Further, at least one window is identified as beingactive. For example, a single window may be rendered in two portions 732and 736 that are displayed on the first touch sensitive screen 110 andthe second touch sensitive screen 114. The single window may only occupya single position in the window stack 728 although it is displayed onboth displays 110, 114.

Yet another arrangement of a window stack 760 is shown in FIGS. 7Cthrough 7E. The window stack 760 is shown in three “elevation” views. InFIG. 7C, the top of the window stack 760 is shown. Two sides of thewindow stack 760 are shown in FIGS. 7D and 7E. In this embodiment, thewindow stack 760 resembles a stack of bricks. The windows are stacked oneach other. Looking from the top of the window stack 760 in FIG. 7C,only the top most windows in the window stack 760 are seen in differentportions of the composite display 764. The composite display 764represents a logical model for the entire display area of the device100, which can include touch sensitive display 110 and touch sensitivedisplay 114. A desktop 786 or a window can occupy part or all of thecomposite display 764.

In the embodiment shown, the desktop 786 is the lowest display or“brick” in the window stack 760. Thereupon, window 1 782, window 2 782,window 3 768, and window 4 770 are layered. Window 1 782, window 3 768,window 2 782, and window 4 770 only occupy a portion of the compositedisplay 764. Thus, another part of the stack 760 includes window 8 774and windows 5 through 7 shown in section 790. Only the top window in anyportion of the composite display 764 is actually rendered and displayed.Thus, as shown in the top view in FIG. 7C, window 4 770, window 8 774,and window 3 768 are displayed as being at the top of the display indifferent portions of the window stack 760. A window can be dimensionedto occupy only a portion of the composite display 760 to “reveal”windows lower in the window stack 760. For example, window 3 768 islower in the stack than both window 4 770 and window 8 774 but is stilldisplayed. A logical data structure to manage the window stack can be asdescribed in conjunction with FIG. 8.

When a new window is opened, the newly activated window is generallypositioned at the top of the stack. However, where and how the window ispositioned within the stack can be a function of the orientation of thedevice 100, the context of what programs, functions, software, etc. arebeing executed on the device 100, how the stack is positioned when thenew window is opened, etc. To insert the window in the stack, theposition in the stack for the window is determined and the touchsensitive display 110, 114 to which the window is associated may also bedetermined. With this information, a logical data structure for thewindow can be created and stored. When user interface or other events ortasks change the arrangement of windows, the window stack(s) can bechanged to reflect the change in arrangement. It should be noted thatthese same concepts described above can be used to manage the one ormore desktops for the device 100.

A logical data structure 800 for managing the arrangement of windows ordesktops in a window stack is shown in FIG. 8. The logical datastructure 800 can be any data structure used to store data whether anobject, record, file, etc. The logical data structure 800 can be storedin any type of database or data storage system, regardless of protocolor standard. In embodiments, the logical data structure 800 includes oneor more portions, fields, attributes, etc. that store data in a logicalarrangement that allows for easy storage and retrieval of theinformation. Hereinafter, these one or more portions, fields,attributes, etc. shall be described simply as fields. The fields canstore data for a window identifier 804, dimensions 808, a stack positionidentifier 812, a display identifier 816, and/or an active indicator820. Each window in a window stack can have an associated logical datastructure 800. While only a single logical data structure 800 is shownin FIG. 8, there may be more or fewer logical data structures 800 usedwith a window stack (based on the number of windows or desktops in thestack), as represented by ellipses 824. Further, there may be more orfewer fields than those shown in FIG. 8, as represented by ellipses 828.

A window identifier 804 can include any identifier (ID) that uniquelyidentifies the associated window in relation to other windows in thewindow stack. The window identifier 804 can be a globally uniqueidentifier (GUID), a numeric ID, an alphanumeric ID, or other type ofidentifier. In embodiments, the window identifier 804 can be one, two,or any number of digits based on the number of windows that can beopened. In alternative embodiments, the size of the window identifier804 may change based on the number of windows opened. While the windowis open, the window identifier 804 may be static and remain unchanged.

Dimensions 808 can include dimensions for a window in the compositedisplay 760. For example, the dimensions 808 can include coordinates fortwo or more corners of the window or may include one coordinate anddimensions for the width and height of the window. These dimensions 808can delineate what portion of the composite display 760 the window mayoccupy, which may the entire composite display 760 or only part ofcomposite display 760. For example, window 4 770 may have dimensions 880that indicate that the window 770 will occupy only part of the displayarea for composite display 760, as shown in FIGS. 7c through 7E. Aswindows are moved or inserted in the window stack, the dimensions 808may change.

A stack position identifier 812 can be any identifier that can identifythe position in the stack for the window or may be inferred from thewindow's control record within a data structure, such as a list or astack. The stack position identifier 812 can be a GUID, a numeric ID, analphanumeric ID, or other type of identifier. Each window or desktop caninclude a stack position identifier 812. For example, as shown in FIG.7A, window 1 704 in stack 1 760 can have a stack position identifier 812of 1 identifying that window 704 is the first window in the stack 760and the active window. Similarly, window 6 724 can have a stack positionidentifier 812 of 3 representing that window 724 is the third window inthe stack 760. Window 2 708 can also have a stack position identifier812 of 1 representing that window 708 is the first window in the secondstack 764. As shown in FIG. 7B, window 1 744 can have a stack positionidentifier 812 of 1, window 3, rendered in portions 732 and 736, canhave a stack position identifier 812 of 3, and window 6 756 can have astack position identifier 812 of 6. Thus, depending on the type ofstack, the stack position identifier 812 can represent a window'slocation in the stack.

A display identifier 816 can identify that the window or desktop isassociated with a particular display, such as the first display 110 orthe second display 114, or the composite display 760 composed of bothdisplays. While this display identifier 816 may not be needed for amulti-stack system, as shown in FIG. 7A, the display identifier 816 canindicate whether a window in the serial stack of FIG. 7B is displayed ona particular display. Thus, window 3 may have two portions 732 and 736in FIG. 7B. The first portion 732 may have a display identifier 816 forthe first display while the second portion 736 may have a displayidentifier 816 for the second display 114. However, in alternativeembodiments, the window may have two display identifiers 816 thatrepresent that the window is displayed on both of the displays 110, 114,or a display identifier 816 identifying the composite display. Inanother alternate embodiment, the window may have a single displayidentifier 816 to represent that the window is displayed on both of thedisplays 110, 114.

Similar to the display identifier 816, an active indicator 820 may notbe needed with the dual stack system of FIG. 7A, as the window in stackposition 1 is active and displayed. In the system of FIG. 7B, the activeindicator 820 can indicate which window(s) in the stack is beingdisplayed. Thus, window 3 may have two portions 732 and 736 in FIG. 7.The first portion 732 may have an active indicator 820 while the secondportion 736 may also have an active indicator 820. However, inalternative embodiments, window 3 may have a single active indicator820. The active indicator 820 can be a simple flag or bit thatrepresents that the window is active or displayed.

An embodiment of a method 900 for creating a window stack is shown inFIG. 9. While a general order for the steps of the method 900 is shownin FIG. 9. Generally, the method 900 starts with a start operation 904and ends with an end operation 928. The method 900 can include more orfewer steps or can arrange the order of the steps differently than thoseshown in FIG. 9. The method 900 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method900 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-8.

A multi-screen device 100 can receive activation of a window, in step908. In embodiments, the multi-screen device 100 can receive activationof a window by receiving an input from the touch sensitive display 110or 114, the configurable area 112 or 116, a gesture capture region 120or 124, or some other hardware sensor operable to receive user interfaceinputs. The processor may execute the Task Management Module 540 mayreceive the input. The Task Management Module 540 can interpret theinput as requesting an application task to be executed that will open awindow in the window stack.

In embodiments, the Task Management Module 540 places the user interfaceinteraction in the task stack 552 to be acted upon by the DisplayConfiguration Module 568 of the Multi-Display Management Module 524.Further, the Task Management Module 540 waits for information from theMulti-Display Management Module 524 to send instructions to the WindowManagement Module 532 to create the window in the window stack.

The Multi-Display Management Module 524, upon receiving instruction fromthe Task Management Module 540, determines to which touch portion of thecomposite display 760, the newly activated window should be associated,in step 912. For example, window 4 770 is associated with the a portionof the composite display 764 In embodiments, the device state module 574of the Multi-Display Management Module 524 may determine how the deviceis oriented or in what state the device is in, e.g., open, closed,portrait, etc. Further, the preferences module 572 and/or requirementsmodule 580 may determine how the window is to be displayed. The gesturemodule 576 may determine the user's intentions about how the window isto be opened based on the type of gesture and the location of where thegesture is made.

The Display Configuration Module 568 may use the input from thesemodules and evaluate the current window stack 760 to determine the bestplace and the best dimensions, based on a visibility algorithm, to openthe window. Thus, the Display Configuration Module 568 determines thebest place to put the window at the top of the window stack 760, in step916. The visibility algorithm, in embodiments, determines for allportions of the composite display, which windows are at the top of thestack. For example, the visibility algorithm determines that window 3768, window 4 770, and window 8 774 are at the top of the stack 760 asviewed in FIGS. 7C through 7E. Upon determining where to open thewindow, the Display Configuration Module 568 can assign a displayidentifier 816 and possibly dimensions 808 to the window. The displayidentifier 816 and dimensions 808 can then be sent back to the TaskManagement Module 540. The Task Management Module 540 may then assignthe window a stack position identifier 812 indicating the window'sposition at the top of the window stack.

In embodiments, the Task Management Module 540 sends the window stackinformation and instructions to render the window to the WindowManagement Module 532. The Window Management Module 532 and the TaskManagement Module 540 can create the logical data structure 800, in step924. Both the Task Management Module 540 and the Window ManagementModule 532 may create and manage copies of the window stack. Thesecopies of the window stack can be synchronized or kept similar throughcommunications between the Window Management Module 532 and the TaskManagement Module 540. Thus, the Window Management Module 532 and theTask Management Module 540, based on the information determined by theMulti-Display Management Module 524, can assign dimensions 808, a stackposition identifier 812 (e.g., window 1 782, window 4 770, etc.), adisplay identifier 816 (e.g., touch sensitive display 1 110, touchsensitive display 2 114, composite display identifier, etc.), and anactive indicator 820, which is generally always set when the window isat the “top” of the stack. The logical data structure 800 may then bestored by both the Window Management Module 532 and the Task ManagementModule 540. Further, the Window Management Module 532 and the TaskManagement Module 540 may thereinafter manage the window stack and thelogical data structure(s) 800.

An embodiment of a method 1000 for executing an application, such as aphone application, is shown in FIG. 10. A general order for the steps ofthe method 1000 is shown in FIG. 10, but the method may have a differentorder of steps in some embodiments. Generally, the method 1000 startswith a start operation 1004 and ends with an end operation 1040. Themethod 1000 can include more or fewer steps or can arrange the order ofthe steps differently than those shown in FIG. 10. The method 1000 canbe executed as a set of computer-executable instructions executed by acomputer system and encoded or stored on a computer readable medium.Hereinafter, the method 1000 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-9.

An application, such as a phone application, is executed, in step 1008.In embodiments, a processor 204 receives indication to execute anapplication through a user interface 110, 114, 112, 116, etc. Theindication can be a selection of an icon associated with theapplication. In other embodiments, the indication can be a signalgenerated from another application or event, such as receiving a phonecall or other communication, which causes the application to executeautomatically. The processor 204 can retrieve the application 564 a fromthe application store 560 and begin its execution. In executing theapplication 564 a, a user interface can be generated for a user.

In creating a user interface, the application 564 a can begin executingto create a manifest, in step 1012. A manifest is a data structure thatindicates the capabilities of the application 564 a. The manifest cangenerally be created from the resources in the resources directory ofthe application 564 a. The resources directory can indicate the types ofmodes, locations, or other indications for how the user interface shouldbe configured in the multi-display device 100. For example, the severalmodes can include: “classic mode” that indicates that the application564 a is capable of being displayed on a single screen or display110/114; “dual mode” that indicates that the application 564 a iscapable of being displaced on two or more displays 110 and 114; “maxmode” that indicates the application 564 a is capable of being displayedor desires to be displayed across multiple displays 110 and 114; and/or“bilateral mode” that indicates that the application 564 a is capable ofbeing displayed on 2 or more displays 110 and 114 when the device 100 isin easel mode (see FIG. 1I and/or 1J).

Similarly, the manifest can include a desired or allowed location withinthe displays 110/114. The possible locations can include: “left”, whichindicates that the application 564 a desires to be displayed on the leftdisplay 110; “right”, which indicates that the application 564 a desiresto be displayed on the right display 114; and/or other indications ofwhere a location should be including possible “top” and/or “bottom” ofone or more of the displays 110/114.

The application 564 a can also indicate that it desires to be displayedin a “minimum” window, which is a window that occupies less than thefull area of a single display. There may be other modes possible for theapplication 564 a, which may be included in the manifest. The manifestcan be sent from the application 564 a to the multi-display managementmodule 524.

The multi-display management module 524 can receive the manifest, instep 1016. In receiving the manifest, the multi-display managementmodule 524 can use the information to determine a display binding forthe application 564 a. The manifest may be received more than once fromthe application 564 a based on changes in how the application 564 a isbeing executed, where the application 564 a desires to have a differentdisplay setting for the new mode. Thus, with the manifest, theapplication 564 a can indicate to the multi-display management module524 how best to arrange or what is the desired arrangement for theapplication's user interface. The multi-display management module 524can use the information in the manifest to determine the best fit forthe user interface depending on how the device 100 is currentlyconfigured.

The multi-display management module 524 can determine the applicationdisplay mode, in step 1020. Here the multi-display management module 524receives or retrieves an indication of the device 100 configuration. Forexample, the multi-display management module 524 can determine if thedevice is in single display configuration (see FIG. 6A, 6B, 6D, or 6E),dual display configuration (see FIG. 6C or 6F), bilateral displayconfiguration (see FIG. 6G or 6H), or one of the other displayconfigurations (see FIG. 6I or 6J).

Further, the multi-display management module 524 can determine if thedevice 100 is in a portrait or landscape orientation. With thisinformation, the multi-display management module 524 may then considerthe capabilities or preferences listed for the application 564 a in thereceived manifest. The combined information may then allow themulti-display management module 524 to determine a display binding. Thedisplay binding can include which of the one or more displays 110 and/or114 are going to be used to display the application's user interface(s).For example, the multi-display management module 524 can determine thatthe primary display 110, the secondary display 114, or all displays 110and 114 of the device 100 will be used to display the application's userinterface.

The display modes setting can be assigned by creating or setting anumber in the display binding. This number can be “0” for the primarydisplay 110, “1” for the secondary display 114, or “2” for dual displays110 and 114. The display mode setting can also indicate if theapplication 564 a should display the user interface in portrait orlandscape orientation. Further, there may be other settings, forexample, providing a max mode or other setting that may indicate how theapplication 564 a is to be displayed on the device. The display bindinginformation is stored in a data structure to create and set a binding,in step 1024.

The established display binding may then be provided, by themulti-display management module 524, to the application 564 a, in step1028. The provided display binding data structure can become anattribute of the application 564 a. An application 564 a maythereinafter store the display binding attribute in the memory of thedevice 100. The application 564 a with the display binding may thengenerate a user interface based on this display binding. The application564 a may be unaware of the position of the display 110/114 but may beable to determine, from the display binding, the size of the availableuser interface to generate a window that has particular characteristicsfor that display setting.

When a configuration change happens to the device 100, the multi-displaymanagement module 524 may change the display binding and send a newdisplay binding to the application 564 a. In embodiments, themulti-display management module 524 may indicate to the application 564a that there is a new binding or, in other embodiments, the application564 a may request a display configuration change or a new displaybinding, in which case the multi-display management module 524 may senda new display binding to the application 564 a. Thus, the multi-displaymanagement module 524 can change the configuration of the display forthe application 564 a by altering the display binding for theapplication 564 a during the execution of that application 564 a.

The multi-display management module 524 thereinafter, while theapplication 564 a is executing, can determine if there has been aconfiguration change to the device 100, in step 1032. The configurationchange may be an event (see FIGS. 3A and 3B) triggered by one or moresignals from one or more hardware sensor 172, 176, etc. For example, ifthe device 100 is changed from portrait 304 to landscape 340orientation, Hall effect sensors 172 may indicate to the framework 520that a display configuration change has been made. Other changes mayinclude transitions from a single display 304 to a dual displayconfiguration 320, by opening the device. Other types of configurationchanges may be possible and may be signaled to alert the multi-displaymanagement module 524 of the configuration change. If a configurationchange has been made, the method 1000 proceeds YES to step 1020 so thatthe multi-display management module 524 can determine new applicationdisplay mode settings and create a new display binding, which may bepassed to the application 564 a. If there are no configuration changes,the method 1000 proceeds NO to step 1036.

In step 1036, a new application mode change may be determined.Application mode changes can also occur in the application 564 a, andthus, the application 564 a can determine if something has occurredwithin the application 564 a that requires a different display setting.Modes are described hereinafter with respect to FIG. 51. The mode changecan create a desire to change the display 110/114, and thus, require theapplication 564 a to generate a new manifest. If the application 564 adoes sense a mode change or an event has occurred that requires a changein display setting, the method 1000 proceeds YES back to step 1012. Atstep 1012, a new manifest or preference is created by the application564 a that may be received by the multi-display management module 524 todetermine if the multi-display management module 524 can change thedisplay binding. If it is possible to provide the preferred display, themulti-display management module 524 can create a new display binding andsend display binding back to the application 564 a and allow theapplication 564 a to alter its user interface. If no mode change issensed or an event is not received to create a mode change, the method1000 proceeds NO to end operation 1040.

Unified System:

An embodiment of a unified system 1100 is shown in FIG. 11. Inembodiments, the unified system 1100 includes a computer system 1104 andthe device 100. The computer system 1104 may be as described inconjunction with FIG. 11. The device 100 may be as described herein inconjunction with FIG. 1A through FIG. 10. The device 100 may bephysically connected to the computer system 1104 with a docking cradleor other wired connection. In other embodiments, the device 100 andcomputer system 1104 may communicate or be connected wirelessly using awireless system and/or protocol (e.g., BLUETOOTH™, 802.11g, etc.). Uponconnection of the device 100 and the computer system 1104, the device100 can recognize the connection either manually (through user input) orautomatically and functionally connect the device 100 with the computersystem 1104 to form the unified system. The unified system 1100functions as to allow the device 100 to communicate with, interact with,and/or control the function of the computer system 1104 whenfunctionally connected. As such, when executed, the unified systemappears to be a single system where the device 100 and the computersystem 1104 function in concert. The components and/or software thatenable the unified system, the communications or functions of theunified system, and other description of the unified system is describedin U.S. Provisional Applications 61/507,206, 61/507,201, 61/507,199,61/507,209, 61/507,203, and 61/389,117, which are each incorporatedherein, by reference, for all that they teach and for all purposes.Further, the unified system is also described in U.S. patent applicationSer. Nos. 12/948,585 and 12/948,676, which are each incorporated herein,by reference, for all that they teach and for all purposes.

FIG. 11 illustrates one embodiment of a computer system 1100 upon whichthe test system may be deployed or executed. The computer system 1100 isshown comprising hardware elements that may be electrically coupled viaa bus 1155. The hardware elements may include one or more centralprocessing units (CPUs) 1105; one or more input devices 1110 (e.g., amouse, a keyboard, etc.); and one or more output devices 1115 (e.g., adisplay device, a printer, etc.). The computer system 1100 may alsoinclude one or more storage devices 1120. By way of example, storagedevice(s) 1120 may be disk drives, optical storage devices, solid-statestorage devices, such as a random access memory (“RAM”) and/or aread-only memory (“ROM”), which can be programmable, flash-updateable,and/or the like.

The computer system 1100 may additionally include a computer-readablestorage media reader 1125; a communications system 1130 (e.g., a modem,a network card (wireless or wired), an infra-red communication device,etc.); and working memory 1140, which may include RAM and ROM devices asdescribed above. In some embodiments, the computer system 1100 may alsoinclude a processing acceleration unit 1135, which can include a DSP, aspecial-purpose processor and/or the like.

The computer-readable storage media reader 1125 can further be connectedto a computer-readable storage medium, together (and, optionally, incombination with storage device(s) 1120) comprehensively representingremote, local, fixed, and/or removable storage devices plus storagemedia for temporarily and/or more permanently containingcomputer-readable information. The communications system 1130 may permitdata to be exchanged with the network 1120 and/or any other computerdescribed above with respect to the system 1100. Moreover, as disclosedherein, the term “storage medium” may represent one or more devices forstoring data, including read only memory (ROM), random access memory(RAM), magnetic RAM, core memory, magnetic disk storage mediums, opticalstorage mediums, flash memory devices, and/or other machine readablemediums for storing information.

The computer system 1100 may also comprise software elements, shown asbeing currently located within a working memory 1140, including anoperating system 1145 and/or other code 1150, such as program codeimplementing the components and software described herein. It should beappreciated that alternate embodiments of a computer system 1100 mayhave numerous variations from that described above. For example,customized hardware might also be used and/or particular elements mightbe implemented in hardware, software (including portable software, suchas applets), or both. Further, connection to other computing devicessuch as network input/output devices may be employed.

Unified Desktop:

An embodiment of a unified desktop 1300 is shown in FIG. 13. The unifieddesktop 1330 is the user interface for the unified system 1100. Thus,the unified desktop 1300 is formed from the user interface 1304 in thescreen 1215 associated with the computer system 1104 and the userinterface 1308 in the screen(s) 104, 108 associated with the device 100.As a unified desktop 1300, the user interface 1304 and 1308 functiontogether to provide parallel displays, exchange windows or other userinterface elements, and generally present a cohesive user interfaceacross both the computers system 1104 and the device 100. In otherwords, the unified desktop spans or is provided over at least one of thescreens 104, 108 of the device 100 and the screen 1215 of the computersystem 1104. The device 100 can assume the form factor and function ofboth device 100 and the computer system 1104; the design of the unifieddesktop can provide a seamless user experience across the device 100 andthe computer system 1104, enabling the user to access shared content,manage applications and peripherals regardless of which system 100 or1104 presents the user interface action. Hereinafter, specific userinterface actions related to the unified desktop shall be presented.

Status Indicators:

A portion of the unified desktop is shown in FIG. 14. More particularly,the user interface 1304 of the unified desktop 1300 is shown, where aset of status indicators are provided in a portion 1400 of the unifieddesktop 1300. The status indicators in the portion 1400 provideinformation about both the device 100 and the computer system 1104. Inembodiments, the portion 1400 is provided in only one of the userinterface 1304 or user interface 1308. Thus, status indicatorsassociated with both the device 100 and the computer system 1104 areshown together in a screen 1215 or 104, 108 associated with only thedevice 100 or the computer system 1104.

The status indicators shown in FIG. 14 include a wireless fidelityindicator 1404, a BLUETOOTH indicator 1408, a Network Traffic indicator1412, a signal strength indicator 1416, a battery indicator 1420, apower menu indicator 1430, and a time indicator 1434. In embodiments,one or more of the indicators may be selectable to provide furtherinformation or user interface devices that may be selected to configurethe device 100 and/or the computer system 1104. For example, as shown inFIG. 14, the battery indicator 1420 has been selected, which caused thedevice 100 to provide a drop down user interface device 1425 in the userinterface 1304. The drop down user interface device 1425 providesfurther information 1438 about the amount of device battery life and auser interface device 1442 that can be selected to access the powersettings for the device 100. Thus, the user can configure the device 100or the computer system 1104 by accessing menus or other user interfacethrough the status indicators 1404 through 1434. Some of the possiblestatus indicators that may be displayed for the device 100, and themenus or other information associated with the status indicators isprovided in the table below:

Indicator Menu content Description Label Wireless Wireless Presents thecurrent “Wireless fidelity: <x>”, where <x> fidelity fidelity statusstatus of Wireless stands for “Off”, “Scanning . . . ”, fidelity.“Connecting to <SSID> . . . ”, “Disconnected”, “Connected”. WirelessAllows for turning “Turn Wireless fidelity on”, or “Turn fidelity ON/OFFWireless fidelity on Wireless fidelity off” toggle and off. List offound Lists all the Wireless “<SSID>” and an icon to represent theWireless fidelity fidelity networks that network's strength and itssecurity. The networks are found and known. network currently connectedto is List of networks is marked. scanned whenever the menu isdisplayed. When clicked, tries to connect to the network, and shows adialog if a password is required. Command to Allows for “Add Wirelessfidelity network . . . ” connect to a connecting to a hidden Wirelesshidden Wireless fidelity network fidelity network. Shows a dialog forentering the SSID, a dropdown menu for security protocols, and apassword field when required. Based on the same command in ANDROIDSettings. Link to Links to: ANDROID “Wireless fidelity settings . . . ”Wireless fidelity Settings > Wireless settings & network settingsBLUETOOTH BLUETOOTH The BLUETOOTH “<device name>” device name name ofthe handset. BLUETOOTH Presents the current “BLUETOOTH: <x>”, where <x>status status of stands for “On”, or “Off” BLUETOOTH. BLUETOOTH Allowsfor turning “Turn BLUETOOTH on”, or “Turn ON/OFF toggle BLUETOOTH onBLUETOOTH off” and off. Discoverability Turns on the “Makediscoverable”, or “Discoverable status discoverability of for <x>seconds” BLUETOOTH for 120 seconds (ANDROID default) List of Lists allpaired and <BLUETOOTH device name> + icon connected currently connectedrepresenting the type of the device BLUETOOTH BLUETOOTH devices devices.List of devices is updated whenever the menu is displayed. Items are notclickable. Link to Links to: ANDROID “BLUETOOTH devices & settings . . .” BLUETOOTH Settings > Wireless settings & network settings > BLUETOOTHsettings Network traffic Network status Shows the current “Network:<x>”, where <x> stands for network speed (3G, the network speed 2G, . .. ) Link to Links to: Settings > “Mobile network settings . . . ”Network Mobile networks settings Signal strength Network status Showsthe current “<operator name>” operator Network Shows the current “Signalstrength: <x>”, where <x> strength signal strength stands for “none”,“poor”, “good”, “very good”, “excellent” When airplane mode is on:“Airplane mode” Link to Links to: Settings > “Mobile network settings .. . ” Network Mobile networks settings Battery Battery status Shows thestatus of “Phone battery: <x>%”, when using (phone) the handset'sbattery battery power; <x> stands for the current charge. charge. “Phonebattery charging (<x>%)”, when the battery is being charged; <x> standsfor the current “Phone battery charged”, when the battery is fullycharged and plugged in. Battery Battery status Shows the status of“Peripheral battery: <x>%”, when (peripheral, the second battery, usingbattery power; <x>stands for the when provided by a current charge.applicable) peripheral. “Peripheral battery charging (<x>%)”, when thebattery is being charged; <x> stands for the current charge. “Peripheralbattery charged”, when the battery is fully charged and plugged in. GPSGPS status Shows the current “GPS status: <x>”, where <x> stands statusof the GPS for “On”, “Off”, or “Failure” GPS ON/OFF Allows for turning“Turn GPS on”, or “Turn GPS off” toggle BLUETOOTH on and off. Link toGPS Links to: Settings > “Location settings . . . ” settings Location &Security Sync Sync status Shows the current “Syncing in progress . . . ”status of the Sync Link to Sync Links to: Settings > “Sync settings . .. ” settings Account & Sync Alarms Integrated into date/time menu No SIMWarning A warning message “No SIM card. Emergency calls only.” warningmessage for not finding a SIM card Speakerphone Speakerphone Shows thestatus of “Speaker on” status speakerphone when in use Roaming Roamingstatus Shows roaming “Roaming” warnings warnings Link to Links to:Settings > “Mobile network settings . . . ” Network Mobile networkssettings TTY TTY status Shows the Text “TTY enabled” Telephone Device orTelecommunication Device for the Deaf (TDD) status

Some of the possible status indicators that may be displayed for thecomputer system 1104, and the menus or other information associated withthe status indicators is provided in the table below:

Indicator Menu content Description Label Volume (and Silent mode Turnson silent mode “Turn Silent mode on”, or “Turn Silent silent/vibration)toggle mode off” Volume slider Allows for changing the volume level;Link to Sound Links to: “Sound settings . . . ” settings Monitors UseUnity menu For settings label, use “Monitor settings . . . ” KeyboardUse Unity menu For settings label, use “Keyboard settings . . . ”Time/date Use Unity menu List of alarms Lists all alarms that “<alarmname>: <alarm time> - <repeat have been set up and days>”; note that thealarm name and enabled. Only shown repeat days are optional. Examples:8:30 when alarms have AM - Mon, Tue, Wed, Thu, Fri 10:00 been set up.AM - Sat, Sun Groceries: 6:40 PM Pills: 12:00 PM - Mon, Tue, Wed, Thu,Fri Link to Clock Opens the Android “Manage alarms . . . ” applicationClock application. Only shown when alarms have been set up. Link toelate & Links to: Settings > “Date & time settings . . . ” time settingsDate & time settings Power menu Airplane mode Toggle airplane “TurnAirplane mode on”, or “Turn mode on and off Airplane mode off” SleepSleep “Sleep” Power off Power off “Power off” Android Links to Android“Phone settings . . . ” Settings Settings application PC Settings Linksto PC system “Desktop settings . . . ” settings

Other possible status indicators are contemplated and included as oneskilled in the art would understand.

A user interface 1308 with other status indicators is shown in FIG. 15.User interface 1308 is associated with the device 100. The userinterface 1308 may also include a portion 1500 that displays statusindicators. In embodiments, the portion 1500 may include the same ordifferent status indicators from portion 1400 and may display the statusindicators substantially simultaneously with portion 1400. For example,portion 1500 may include a Network Traffic indicator 1412, a signalstrength indicator 1416, a battery indicator 1420, and a time indicator1434. However, portion 1500 may include an alarm indicator 1504 that isnot shown in portion 1400. Thus, the portions 1400 and 1500 can show thesame indicators, different indicators, and, in some embodiments,indicators associated with only the device 100 or the computer system1104.

An embodiment of a method 1600 for providing status indicators is shownin FIG. 16. While a general order for the steps of the method 1600 isshown in FIG. 16. Generally, the method 1600 starts with a startoperation 1604 and ends with an end operation 1624. The method 1600 caninclude more or fewer steps or can arrange the order of the stepsdifferently than those shown in FIG. 16. The method 1600 can be executedas a set of computer-executable instructions executed by a computersystem and encoded or stored on a computer readable medium. Hereinafter,the method 1600 shall be explained with reference to the systems,components, modules, software, data structures, user interfaces, etc.described in conjunction with FIGS. 1-15.

A computer system 1104 and a device 100 can be connected, physically,electrically, wirelessly, etc. The device 100 can automaticallyrecognize the connection and functionally connect the device 100 withthe computer system 1104 to form a unified system 1100, in step 1608. Inother embodiments, a user may provide input to functionally connect thedevice 100 with the computer system 1104. In response to the functionconnection, the device 100 can generate a unified desktop 1300, in step1612. The unified desktop 1300 can expand or create a single userinterface for the unified system 1100 across the screens of the device100 and the computer system 1104.

The device 100 may then determine status indicators that would need tobe displayed for the user, in step 1616. In embodiments, the device 100can request or discover the status indicators associated with thecomputer system 1104. The status indicators associated with the computersystem 1104 may be incorporated into a data structure or combined withthe status indicators associated with the device 100. The combined setof status indicators may then be provided in the unified desktop 1300,in step 1620. For example, the combined set of status indicators can bedisplayed in a portion 1400 of the user interface 1304. Thus, in asingle area of the unified desktop 1300 (and possibly only on one screenof either the device 100 or the computer system 1104), the device 100can provide status indicators for both the device 100 and the computersystem 1104.

An embodiment of a method 1700 for providing status indicators is shownin FIG. 17. While a general order for the steps of the method 1700 isshown in FIG. 17. Generally, the method 1700 starts with a startoperation 1704 and ends with an end operation 1724. The method 1700 caninclude more or fewer steps or can arrange the order of the stepsdifferently than those shown in FIG. 17. The method 1700 can be executedas a set of computer-executable instructions executed by a computersystem and encoded or stored on a computer readable medium. Hereinafter,the method 1700 shall be explained with reference to the systems,components, modules, software, data structures, user interfaces, etc.described in conjunction with FIGS. 1-16.

The processor 204 of the device 100 can receive a selection of a statusindicator, in step 1708. A selection can be a user interface actionconducted on a status indicator. For example, a user may hover a pointerover status indicator 1420. In another example, the user may click thepointer on the status indicator 1420 to select it. Regardless, the userconducts a user interface action on a status indicator to generate aninput into the unified desktop 1300. In response to receiving theselection by the user, the device 100 can provide information and/or auser interface device in the unified desktop 1300, in step 1712.Information can include more detail about a status, as described in thetables above. For example, upon selecting the status indicator 1420, thedevice 100 can provide more detailed information that the battery chargeis at 50%, as shown in information 1438 in the drop down 1434. A userinterface device may be a selectable icon or other user interfacedisplay that will allow the user to access further functionality. Forexample, the user interface display 1442 in the drop down 1424 displaycan be selected by the user's pointer. Selection of the user interfacedisplay 1442 allows the user to access power settings for the device100. Other menus or functions can be accessed through the statusindicators as shown in the tables above.

The processor 204 of the device 100 can receive a selection of a userinterface device, in step 1716. For example, the user may select userinterface display 1442 by clicking on or near the user interface display1442. Upon receiving this selection, the device 100 can provide a menuor other functionality associated with the status indicator, in step1720. In embodiments, the device 100 presents a menu that can alter oraddress the status indicated by the status indicator. The menus orfunctionality that may be accessed may be as described in the tablesabove. For example, by selecting user interface display 1442, the devicemay provide a power settings menu to the user that allows the user tochange the power settings of the device 100. The user may modify afunction of the device 100 or the computer system 1104 by interactionwith the provided menu or functionality. For example, the user maychange the duration of inactivity required before a screen blacks out inthe power settings menu.

Freedom Window Mode:

A unified desktop interface 1304 is shown with a window 1800 (showing apersonal computing application user interface) and a freeform window1804 in FIG. 18. A freeform window 1804 is a shell that can encapsulatea user interface for a device application. A device application can beany application that typically executes on the device 100. Thus, thedevice application may be configured to execute in a mobile deviceenvironment but not in a personal computing environment. The deviceapplication can be specific to the device and does not execute on thecomputer system. For example, gestures received with the device 100 canaffect the device application but may not be received or understood inthe personal computing environment. Device applications can include aphone application, a text messaging application, a utilitiesapplication, a game application, or a mobile application. The deviceapplication may be executed by the device 100 receiving a user selectionof the device application. The selection may be a user selection of ashortcut displayed in the unified desktop. An example of a shortcut 1812is shown in the user interface 1304. The shortcut 1812 allows a deviceapplication to be opened in the personal computing environment likeother personal computing applications.

The freeform window 1408 allows the device application user interface tobehave as a typical window in a computer system environment. Forexample, as shown in FIG. 18, freeform window 1804 allows the userinterface 1808 of the device application to display at least partiallyover another window 1800. In other embodiments, the freeform window 1804allows the user interface 1808 of the device application to display atleast partially behind another window (not shown). Thus, the freeformwindow 1804 provides display functionality to the user interface 1808that would not normally be functional for a device application.

Upon executing the device application, the device application cangenerate a user interface 1808 which can be incorporated into thefreeform window 1804. An embodiment of the freeform window 1804 is shownin FIG. 19. The freeform window 1804 includes a portion 1900 thatincludes controls 1904-1912. The controls can cause the user interface1808 to complete actions associated with a personal computingenvironment. For example, control 1904 can cause the device 100 to closethe user interface 1808 and stop execution of the device applicationassociated therewith. Control 1908 can cause the device 100 to minimizeor shrink the user interface 1808 of the device application. Control1912 can cause the device 100 to maximize the user interface 1808 of thedevice application. A user may also use handles or other controls toexpand or contract the freeform window 1804 and thus the user interface1808.

The freeform window 1804 can provide one or more user interface devicesthat allow the user interface 1808 to provide functionality (such asfeatures or controls) in the freeform window 1804. For example, a firstuser interface device 1916 may be a control or device to access previousinformation displayed by the user interface 1808 of the deviceapplication. A second user interface device 1924 can provide a controlto exit or stop execution of the device application. A third userinterface device 1928 can provide a feature to expand the user interface1808 the device application into the entire available space of thefreeform window 1804. A fourth user interface device 1920 may provide acontrol to change the user interface 1808 to a second user interfacethat displays other information. Other user interface devices thatprovide other functionality are contemplated as one skilled in the artwould understand.

An embodiment of a method 2000 for providing a freeform window is shownin FIG. 20. A general order for the steps of the method 2000 is shown inFIG. 20, but the method may have a different order of steps in someembodiments. Generally, the method 2000 starts with a start operation2004 and ends with an end operation 2024. The method 2000 can includemore or fewer steps or can arrange the order of the steps differentlythan those shown in FIG. 20. The method 2000 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method2000 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-19.

A computer system 1104 and a device 100 can be connected, physically,electrically, wirelessly, etc. The device 100 can automaticallyrecognize the connection and functionally connect the device 100 withthe computer system 1104 to form a unified system 1100, in step 2008. Inother embodiments, a user may provide input to functionally connect thedevice 100 with the computer system 1104. In response to the functionconnection, the device 100 can generate a unified desktop 1300, in step2012. The unified desktop 1300 can expand or create a single userinterface for the unified system 1100 across the screens of the device100 and the computer system 1104.

The device 100 may then execute a device application, in step 2020. Inembodiments, the device 100 may receive a selection of a deviceapplication from the unified desktop 1300. For example, the user mayselect a shortcut 1812. Regardless, the device 100 can execute theselected device application in the computer system environment. When thedevice 100 executes the device application, a freeform window 1804 maybe created to encapsulate or display the user interface 1808 of thedevice application. Thus, the device 100 displays the user interface1808 of the device application in the freeform window 1804, in step2020.

An embodiment of a method 2100 for providing status indicators is shownin FIG. 21. A general order for the steps of the method 2100 is shown inFIG. 21, but the method may have a different order of steps in someembodiments. Generally, the method 2100 starts with a start operation2104 and ends with an end operation 2124. The method 2100 can includemore or fewer steps or can arrange the order of the steps differentlythan those shown in FIG. 21. The method 2100 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method2100 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-20.

The processor 204 of the device 100 can receive a selection of a deviceapplication, in step 2108. A selection can be a user interface actionconducted on a shortcut 1812 or other user interface device. Regardless,the user conducts a user interface action to execute a deviceapplication. In response to receiving the selection by the user, thedevice 100 can determine any device application feature, controls, orother functionality to be provided for the user interface 1808, in step2112. The features, controls, etc. can be functions that conduct andaction or complete a process for the device application and may notfunction in a typical computer system environment. These functions caninclude expanding or contracting the window, providing alternativedisplays, entering information, executing sub-processes, etc. Somepossible features or controls are as discussed with FIG. 19.

The processor 204 of the device 100 can provide a freeform window 1804for the user interface 1808 of the device application, in step 2116. Thefreeform window 1808 can be as described in FIGS. 18 and 19. As part ofthe freeform window 1808, the device may provide one or more userinterface devices that enable the features or controls determined by thedevice 100, in step 2120. The user interface devices may be as describedin conjunction with FIG. 19.

Wake and Unlock:

FIGS. 22 through 28 show a unified desktop interface 1304 is shown whileis sleep mode or in a state after waking or unlocking after sleep mode.Sleep mode is a mode where the user interface displays are inactive or“blackened”. As shown in FIG. 22, user interface 2204 and user interface2208 do not show any content because the system 2200 is in “sleep mode.”As described herein, the sleep state or sleep mode can include differenttypes of states including a simple sleep state, a screen lock state,and/or a passcode lock state, as described herein. To leave sleep modeand continue to use the system 2200, input may be received from a userin the keyboard 2212, a user interface device 2216, or by other means(e.g., mouse, power button, etc.). If such input is received, the system2200 can change states of a user interface for the unified desktopduring wake, unlock, passcode unlock, call received, and other states.

A table 2900 containing at least some of the possible sleep states andhow to interact with the system 2200 in the state is shown in FIG. 29.In embodiments, there may be three states 2904, a simple “sleep” staterepresented in column 2908, a “screen lock” state represented in column2912, and/or a “passcode lock” state represented in column 2916. Inembodiments, there may be more or fewer states. A sleep state may bechosen by a user and affected when the device 100 receives a selectionof the sleep state from the user.

The table 2900 shows rules that govern the sleep state and how to wakefrom the selected sleep state. In a sleep state, the user interface 1304is off without anything being displayed and the wake action is anyinteraction with the user interfaces of the unified desktop. In a screenlock state, the user interface 1304 is off and the user interface, of atleast the device 100, requires a specified and predetermined userinteraction (e.g., moving a bar on the user interface) to unlock thestate. Generally, the bar or other user interface device that receivesthe specified user interaction is presented to the user after the userprovides an initial user interface interaction to the unified desktop.In a passcode state, the system 2200 requires the entry of a passcode(e.g., a numeric code, a visual code, etc.) to exit the state. As withthe screen lock state, a passcode user interface device that receivesthe passcode is presented to the user after the user provides an initialuser interface interaction to the unified desktop. Thus, all the statesappear as that shown in FIG. 22 but require different input to exit thestate.

At least two events 2920 can cause the system 2200 to leave the statesmentioned above. The first event may be a wake event represented in row2924. The second event may be a phone call represented in row 2928. Whenthese events occur, with the correct user input shown in the body oftable 2900, the system 2200 may exit from the state and allow the userto use or interact with the system.

An embodiment of a method 3000 for waking the system 2200 is shown inFIG. 30. A general order for the steps of the method 3000 is shown inFIG. 30, but the method may have a different order of steps in someembodiments. Generally, the method 3000 starts with a start operation3004 and ends with an end operation 3032. The method 3000 can includemore or fewer steps or can arrange the order of the steps differentlythan those shown in FIG. 30. The method 3000 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method3000 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-29.

A system 2200 may sleep, in step 3008. The sleep state may include thestates as described in conjunction with FIG. 29 or other states thatrender the system 2200 inactive. The system 2200 may appear as shown inFIG. 22, where in user interface 2204 for the computer system 1104 andthe user interface 2208 for the device 100 are inactive and do notdisplay anything. The sleep state may be entered after the expiration ofa period of time, automatically in response to an action or event, or inresponse to user interaction. Thus, the sleep state can render thesystem 2200 unusable until it is awakened or unlocked.

The device 100 or the computer system 1104 may receive an event in step3012. An event may be as described in conjunction with FIG. 29. Forexample, the event may be a wake action received by a user. Inalternative embodiments, the event may be a received phone call. Eitherevent may be received with the correct user input to wake the system2200. The correct user input is based on the state in which the devicecurrently resides.

Thus, the system 2200 may determine the state of the system, in step3016. The state may be set by the user or be automatically set. Forexample, a user may determine that a passcode lock is necessary andenter the passcode with the setting. However, if the user makes nochange to the desired sleep state, the device 100 may determine to usethe sleep state 2908. Regardless, the system 2200 determines which statehas been set when the device sleeps.

The system 2200 may then determine if the correct user interface input,associated with the determined state, has been entered to wake thesystem 2200, in step 3020. As shown in table 2900, there is differentinput based on the event and the state. If the system 2200 is in asimple sleep state 2908, then any input to the device 100 or computersystem 1304 may wake the system 2200. Thus, the user may hit a key onthe keyboard 2212, push a user interface device 2216 on the device 100,touch the touch sensitive display 110, 114, the gesture capture area120, 124, or another touch-sensitive area on the device 100, or makesome other input into the system 2200. In the screen lock state 2912,the device 100 may require the user to complete some form of user input(e.g., moving a slider bar or other orchestrated movement on the touchsensitive display 110, 114), either in addition to a first interactionor by itself, to unlock the device 100. The computer system 1304 may notrequire any additional input. Thus, a first gesture may wake thecomputer system 1304, while a second gesture is needed to unlock thedevice interface 2208. If the correct input is received, the method 3000proceeds YES to step 3028.

However, if the incorrect input is received, the method 3000 proceeds NOto step 3024, where the system 2200 may inform the user of the incorrectinput. Thus, a user interface may be provided that indicates that theinput was incorrect, for example, a pop-up message that states “Thepassword or username is incorrect.” In other embodiments, the system2200 may revert to the locked state without unlocking the device, whichcan indicate to the user that the input was incorrect. In step 3028, thesystem 2200 may wake. Thus, the system 2200 can transition, for example,for the display shown in FIG. 27 to that shown in FIG. 28. The user maythen have complete access to the system 2200 and view the desktop oropen application after waking the system 2200.

Docking and Undocking

An embodiment of a method 3400 for docking the device 1308 with thecomputer system 1304 to form a unified system 3100 is shown in FIG. 34.A general order for the steps of the method 3400 is shown in FIG. 34,but the method may have a different order of steps in some embodiments.Generally, the method 3400 starts with a start operation 3404 and endswith an end operation 3432. The method 3400 can include more or fewersteps or can arrange the order of the steps differently than those shownin FIG. 34. The method 3400 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method3400 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-33 and FIG. 38. In particular, FIGS. 31-33 showembodiments of user interfaces associated with the process of docking.

A device 1308 and a computer system 1304 may be provided, in step 3408.The device 1308 may be a mobile device as described herein. Inembodiments, the device 1308 may display one or more user interfaces3108 and/or 3112 before docking occurs. The computer system 1104 caninclude a display 1304 that presents a user interface 3104. The userinterface 3104 can include any window or other display. In embodiments,the user interface 3104 shows a slide show in FIG. 31 before docking.After presenting the device 1308 and the computer system 1304, thedevice 1308 may dock with the computer system 1304, in step 3412.

Docking the device 1308 may include electrically connecting the devicewith the computer system 1304. The electrical connection may be madewith a docking cradle, a wire interface, a wireless interface, or byother device or connection. Once docked, the computer system 1304 may becontrolled or managed by the device 1308. Thus, actions on the computersystem 1304 may be handled by the device 1308. Thus, docking the device1308 creates the unified system and presents the unified interface forthe computer system 1304 and the device 1308.

The behavior of the unified system 3200, as shown in FIG. 32 and afterdocking, may be governed by a set of docking rules, as described inconjunction with FIG. 38. In embodiments, the computer system display3204 may hide one or more displays or windows presented before docking.Rather, the computer system 1304 may present a desktop 3208 afterdocking, in step 3416. The desktop 3208 can display a unified desktoptheme with icons or other user interface devices (for example, icon3212) providing access to unified system 3200 functionality. Thus, thecomputer system 1304 hides pre-existing windows or displays to providethe unified desktop 3204.

After docking, the device software (as described in FIGS. 5A and 5B) maydetermine if any application displays or windows were displayed on thedevice 1308 before docking, in step 3420. The determination may includethe processor 504 checking the display configuration in the framebuffers 548 or other type of check. If there were displays presented onthe device 1308 before docking, the method 3400 may proceed YES to step3428. If there were on displays presented on the device 1308 beforedocking, the method 3400 may proceed NO to step 3424 where the unifieddesktop is also provided on the display(s) of the device 1308, as seenin FIG. 33.

If there were on displays (e.g., display 3108 and/or display 3112)presented on the device 1308 before docking, the displays 3108 and/or3112 may be migrated from the device interface 3304 to the computersystem display 3204, as shown in FIG. 33. In embodiments, new freeformwindows or big brother applications are invoked to migrate the displays.Thus, a new instance of the application window or interface is opened inthe display of the computer system. In other embodiments, the displaybuffer is simply changed to reflect the migration. Thus, displays on thedevice 1308 preempt any displays on the computer system 1304 afterdocking.

An embodiment of a method 3700 for undocking the device 1308 with thecomputer system 1304 to is shown in FIG. 37. A general order for thesteps of the method 3700 is shown in FIG. 37, but the method may have adifferent order of steps in some embodiments. Generally, the method 3700starts with a start operation 3704 and ends with an end operation 3728.The method 3700 can include more or fewer steps or can arrange the orderof the steps differently than those shown in FIG. 37. The method 3700can be executed as a set of computer-executable instructions executed bya computer system and encoded or stored on a computer readable medium.Hereinafter, the method 3700 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-36 and FIG. 38.In particular, FIGS. 35 and 36 show embodiments of user interfacesassociated with the process of undocking.

A device 1308 and a computer system 1304 may be docked. The device 1308may be a mobile device as described herein. In embodiments, the device1308 may display one or more user interfaces 3504 before undockingoccurs. The computer system 1104 can include a display 1304 thatpresents a display 3508 before undocking. Thereinafter, the device maybe undocked from the computer system 1304, in step 3708.

Undocking the device 1308 may include electrically disconnecting thedevice from the computer system 1304. The electrical connection may bemade with a docking cradle, a wire interface, a wireless interface, orby other device or connection. To disconnect the device 1308, the device1308 may be separated from the docking cradles or wire interface or thewireless interface may be disconnected. Once undocked, the computersystem 1304 may no longer be controlled or managed by the device 1308.Thus, the computer system 1304 may resume control of its own actions.Thus, undocking the device 1308 dismantles the unified system andpresents separate interfaces for the computer system 1304 and the device1308.

The behavior of the unified system 3200, as shown in FIG. 36 afterundocking, may be governed by a set of undocking rules, as described inconjunction with FIG. 38. In embodiments, the computer system display3204 may hide the unified desktop, in step 3712, and display a window orother display 3604 that was hidden during docking, as shown in FIG. 36.After undocking, the device software (as described in FIGS. 5A and 5B)may determine if any application displays or windows were displayed onthe device 1308 before undocking, in step 3716. The determination mayinclude the processor 504 checking the display configuration in theframe buffers 548 or other type of check. If there were displayspresented on the device 1308 before undocking, the method 3700 mayproceed YES to step 3720. If there were on displays presented on thedevice 1308 before undocking, the method 3700 may proceed NO to step3724 where a device desktop is provided on the display(s) of the device1308.

If there were on displays (e.g., display 3504) presented on the device1308 before undocking, the display(s) 3504 may be maintained on thedevice interface, as shown in FIG. 35. However, no windows or displaysare migrated from the computer system 1304 to the device 1308. Thus, thedevice 1308 maintains its display characteristics after undocking.

A table 3800 containing at least some of the docking and undocking rulesand how to interact with the system 2200 during docking and undocking isshown in FIG. 38. In embodiments, there are two sets of rules 3804—oneset for docking represented in column 3808 and another for undockingrepresented in column 3812. In embodiments, there may be more or fewerrules. Further, the docking rules may include a rule governingvisible-to-visible transitions represented in column 3816 and astickiness rule represented in column 3820. The table 3800 shows rulesthat govern the components (represented by column 3824) of the unifiedsystem. Thus, the rules govern how the displays of the device 1308 andcomputer system 1304 are managed during docking and undocking. Thedevice interfaces are represented in row 3828 while the computer systeminterfaces are represented in row 3832.

During docking, the user interface 1304 may display interfaces or adesktop for the computer system. However, upon docking, the interfacesand computer system desktop are hidden according to thevisible-to-visible rules for the computer system. Further, if there wasa previous docking and undocking, any application interfaces previouslydisplayed during a past docking are re-displayed according to thestickiness rules for the computer system. It should be noted that thedevice or computer system may store an indicator of the previouslydisplayed interfaces at the last docking and access the indicators toreinstate the interfaces upon re-docking. The device, during docking,will have interfaces displayed on the device moved to the display of thecomputer system according to the visible-to-visible rule.

During undocking, any interfaces displayed on the device remaindisplayed on the device according to the undocking rules for the device.For the computer system, applications displayed in the unified desktopare hidden but available if the device is re-docked. The computer systemmay then display other interfaces associated with the computer system orthe computer system desktop, according to the undocking rules for thecomputer system.

An embodiment of a method 4800 for applying a visible-to-visible ruleduring docking of a device is shown in FIG. 48. A general order for thesteps of the method 4800 is shown in FIG. 48, but the method may have adifferent order of steps in some embodiments. Generally, the method 4800starts with a start operation 4804 and ends with an end operation 4840.The method 4800 can include more or fewer steps or can arrange the orderof the steps differently than those shown in FIG. 48. The method 4800can be executed as a set of computer-executable instructions executed bya computer system and encoded or stored on a computer readable medium.Hereinafter, the method 4800 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-47.

Device 1308 docks with a computer system (PC) 1304. As shown in FIG. 39,the device can include two displays 3908 and 3912. The PC can includeone display 3904. When docked, the displays 3904, 3908, and/or 3912 candisplay a unified desktop, which may display one or more applicationwindows. As explained in conjunction with FIG. 38, the unified systemmaintains visible windows from the device 1308 on the unified desktop.Before docking, the PC 1304 and device 1308 may appear as shown in FIG.40. As shown in FIG. 40, the device 1308 may display a first window 3108and a second window 3112. The PC 1304 may display a first window 4004and a second window 4008. Further, the device 1308 may display anapplication manager interface 4012 that displays windows (e.g., 4020) onthe first display 3908 of the device 1304 and an application managerinterface 4016 that displays windows on the second display 3912 of thedevice 1304. The application manager interfaces 4012, 4016 can alsodisplay windows (e.g., 4024) that are not currently displayed on thedisplays 3908, 3912.

A representation of a display buffer or data structure 4100 associatedwith the display 3904 is shown in FIG. 41A. The data structure 4100 canstore information about which windows are displayed before docking. Forexample, data object 4104 is associated with window 4004 and data objectis associated with window 4008. Further, a data object 4112 may beassociated with a desktop displayed on the display 3904. A window stack4116 can represent the windows open, active, or inactive on the displays3908, 3912 before docking the device 1308. For example, data object 4124can represent window 3108, data object 4120 can represent window 3112,and data objects 4128, 4132 can represent the desktop on the device1308.

At some time thereinafter, the device 1308 is docked with the PC 1304 tocreate the unified desktop 4200, as shown in FIG. 42. In response todocking the device 1308, the windows 4004, 4008 previously displayed onthe PC 1304 can be hidden or closed, in step 4808. The desktop 4204 maythen be provided on the PC display 39, in step 4812. A processor on thedevice 1304 can then determine if there were any windows active anddisplayed on the device 1304 before docking, in step 4816. The processorcan scan the window stack 4116 to determine that windows 3108 and 3112were open substantially simultaneously with the docking of the device1304.

After determining the windows that were open on the device 1308 beforedocking, the processor can instruct the PC 1304 to create windows thatare similar to or associated with the programs or applications that werebeing executed on the device 1308. For example, if an Internet Browserwas being executed on the device 1308, a browser application can beopened on the PC 1304. After creating the windows, the active windows3108, 3112 are moved to the created windows. In embodiments, stateinformation for the active windows 3108, 3112 can be used to provide anew instance of the window on the PC 1304. Thus, while, to the user, itappears the window is moved, a new window is actually instantiated. Asshown in FIG. 42, windows 3108, 3112 are now open in display 3904. Theunified desktop 4204, 4208 may be shown on the PC 1304 and the device1308, in step 4828.

In response to the movement of the windows after docking, the processormodifies the window stack, in step 4832. For example, the processorremoves the windows from the window stack 4308, as shown in FIG. 43B.Further, the window stack 4308 is changed to reflect that the unifieddesktop 4312 is displayed on the device display 3912, 3908. Further, theprocessor modifies the computer system display buffer, in step 4836. Forexample, the display buffer 4300 is changed to reflect that windows4124, 4120 are open on the PC display 3908. The unified desktop 4304 mayalso be provided on the display 3904, as shown in the window stack.

While docked, a window 3108 may be moved from the PC display 3904 to thedevice display 3908, as shown in FIG. 44. The display buffer 4500 can bechanged to reflect the move, as shown in FIG. 45A. Thus, the window 4124is no longer shown in the window stack 4500 but shown in the windowstack 4504 in FIG. 45B. Upon undocking, the window 3108 remains visibleon the device 1308. The other window 3112 is no longer shown. Thedisplay buffer 4700 for the PC 1304 can now display the PC desktop 4110but no other windows. The window stack 4704 may remain unchanged, asshown in FIG. 47B.

An embodiment of a method 5400 for maintaining window stickiness duringa re-dock of a device is shown in FIG. 54. A general order for the stepsof the method 5400 is shown in FIG. 54, but the method may have adifferent order of steps in some embodiments. Generally, the method 5400starts with a start operation 5404 and ends with an end operation 5432.The method 5400 can include more or fewer steps or can arrange the orderof the steps differently than those shown in FIG. 54. The method 5400can be executed as a set of computer-executable instructions executed bya computer system and encoded or stored on a computer readable medium.Hereinafter, the method 5400 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-53.

Device 1308 docks with a computer system (PC) 1304, in step 5408. Thedocking is as described herein. During the docking, at least one windowis opened on the unified desktop of the computing system 1304, in step5412. For example, at least one of window 4904 or window 4908 are openedduring the docked session. The docking of the unified system isrepresented by line 4912. In embodiments, a desktop 4916 is shown on thedevice 1308. However, the device 1308 might also have one or more openwindows displayed on the device 1308.

At some time thereinafter, the device 1308 is undocked from the PC 1304,in step 5416. The undocked device 1308 and computer system 1304 is shownin FIG. 50, as system 5000. The undocked system may be represented bythe absence of line 4912. Upon the occurrence of the undock event,recognized by the device 1308 and/or the computer system 1304, thedevice 1308 and/or the computer system 1304 may save a data structure5300, in step 5420. The data structure 5300 is as shown in FIG. 53.

The data structure 5300 may include one or more data fields and may bestored as any type of data structure as described herein. Inembodiments, the data structure 5300 can include a timestamp 5304 of thelast docking, an identifier (ID) for a window 5308, and/or status and/orstate information 5312. The data structure 5300 can include more orfewer data items than that shown in FIG. 53 as represented by ellipses5324. In embodiments, the information contained in data structure 5300is associated with all windows that were open on the computer system1304 before the last undocking. For example, the data structure 5300 mayinclude information about window 4904 and window 4908 as shown in FIG.49.

Further, other data fields, such as window 2 ID 5316 and stateinformation 5320, may represent window 2 4908, which was open on thecomputer system 1304 before undocking. There may be more or fewer datafields for more or fewer windows that may have been open on the computersystem 1304 before undocking, as represented by ellipses 5328. This datastructure 5300 can be stored with the device 1308 and/or the computersystem 1304. The undocked system 5100, as shown in FIG. 51, may have oneor more actions occur on the computer system 1304 or on the device 1308while undocked. For example, window 3 5104 may be opened on the device1308 while the device 1308 is undocked from the unified system.

At some time thereinafter the device 1308 may be re-docked with thecomputer system 1304 to recreate the unified system 5200 as shown inFIG. 52, in system 5424. Upon the occurrence of a re-dock, the computersystem 1304 and/or the device 1308 may recognize the re-dock event andmay access the data structure 5300. Information from the data structure5300 may be read to reopen one or more windows, in step 5428. Forexample, as shown in FIG. 52, window 1 4904 and window 2 4908 may bereopened as having been open during the last docked session. Thus, theopen windows at undocking are sticky or re-open the next time that thedevice 1308 docks with the computer system 1304. Further, windows thatwere open on the device 1308 during undock, may be moved to the computersystem 1304, as represented by window 3 5104 being displayed on thecomputer system display 1308. If a window is moved from the device 1308to the computer system 1304, the desktop 5204 may be displayed on thedevice 1308.

Embodiments of systems 5504/5520 for creating a unified system for thedevice 1308 and PC 1304 are shown in FIGS. 55A and 55B. The softwarecomponents or modules that provide for the unified system on a computersystem are shown in FIG. 55B. The systems 5504 and/or 5520 for thedevice 1308 and the PC 1304 may be stored and executed in hardware asdescribed herein. The software modules can include a first operatingsystem 5508 and a second operating system 5512. The two operatingsystems 5508 and 5512 may interact to create and manage the unifiedsystem. In embodiments, the second operating system 5512 may control thefunctions of the device 1308. The first operating system 5508 maycontrol or direct the operations of the computer system 1304. Thus, thefirst operating system 5508 may communicate with the computer systeminterface 5516 that sends signals to the computing system 1304 throughthe docking hardware. Embodiments of the dual operating system aredescribed in U.S. Provisional Patent Applications 61/507,199, filed Jul.13, 2011, entitled “Dockable Mobile Software Architecture,” 61/507,201,filed Jul. 13, 2011, entitled “Cross-environment communicationframework,” 61/507,203, filed Jul. 13, 2011, entitled “Multi-operatingsystem,” 61/507,206, filed Jul. 13, 2011, entitled “Auto-configurationof a docked system in a multi-OS environment,” and 61/507,209, filedJul. 13, 2011, entitled “Auto-waking of a suspended secondary OS in adockable system”.

The modules on the computer system 5520 may be installed or stored uponthe first docking of the device 1308 to the computer system 1304. Themodules can include a device interface 5524 that communicates with thecomputer interface 5516. Thus, the device interface 5524 can receivesignals from the first operating system 5508 and may send signals orevents to the first operating system 5508. The device interface 5524 cancommunicate with an application-programming interface 5528. In turn, theapplication-programming interface (API) 5528 can communicate with theoperating system 5532 for the computer system. The API 5528 can act asan intermediary that both controls and directs the computing system OS5532 or changes the operation thereof. Thus, the API 5528 can bothsubordinate normal computer system events for the PC 1304 and promotethe events or signals sent from the device 1308.

In embodiments, the API 5528 may include one or more modules. Forexample, the API 5528 can include an interceptor module 5536, a relaymodule 5540, an injector module 5544 and/or a receiver module 5548. Theinterceptor module 5536 may be operable to intercept events or processorexecutions that are put on the stack for the computer system processor.Thus, the interceptor 5536 can erase, delete, or change the stack forthe PC 1304, thus controlling what actions are conducted by the PC 1304.Any events that occur on the PC 1304 that are placed into the stack maybe intercepted by the interceptor 5536 and provided to the relay 5540,which may then relay the event through the device interface 5524 to thefirst operating system 5508. The information sent from the relay 5540allows the first operating system 5508 to respond to the event(s) forthe PC 1304.

Likewise signals from the OS 5508 to the PC 1304 may be received by areceiver 5548. When the first operating system 5508 wants to control orhave the personal computer 1304 conduct some action, the first operatingsystem 5508 may send a signal through the PC interface 5516 to thereceiver 5548. The receiver 5548 may then pass the signal onto theinjector 5544, which may place the event or instruction into the stackfor the computer operating system 5532. Thus, the injector 5544communicates signals to the computer system OS 5532 to control itsactions.

An embodiment of the method 5600 for receiving an event for the unifieddesktop at the device 1308 is shown in FIG. 56. A general order for thesteps of the method 5600 is shown in FIG. 56, but the method may have adifferent order of steps in some embodiments. Generally, the method 5600starts with a start operation 5604 and ends with an end operation 5636.The method 5600 can include more or fewer steps or can arrange the orderof the steps differently than those shown in FIG. 56. The method 5600can be executed as a set of computer-executable instructions executed bya computer system and encoded or stored on a computer readable medium.Hereinafter, the method 5600 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-55B. The process5600 may be described particularly in conjunction with FIGS. 55A and55B.

The operating system 5512 may receive an event at the device 1308, instep 5608. An event may be any type of user interface input or otheroccurrence that may require attention from the device 1308. An event mayrequire action by the device or some type of response. Once an event isreceived, the second operating system 5512 can determine if the event isassociated with the device 1308, in step 5612. For example, if the eventis a user interface input that requires user interface output at thedevice 1308, then the event is related to the device 1308. However, ifthe event may be related to output on the personal computer 1304, thesecond operating system 5512 may determine that the event is related tothe personal computer 1304. If the event is related to the device 1308,the method 5600 proceeds YES to step 5616. In contrast, if the event isnot associated with the device 1308, the method 5600 proceeds NO to step5624.

In step 5616, the second operating system 5512 can process the event forthe device 1308. The processing of an event by an operating system maybe as understood in the art. Thus, the processing of the event mayinvolve user interface output or completing an instruction for anapplication. If the processing requires output, the output may bedisplayed on the interface of the device 1308, in step 5620.

If the event is related to the computer system 1304, operating system 25512 may send the event to the first operating system 5508, in step5624. The first operating system 5508 may process events similarly tothe second operating system 5512 but may process the events for thepersonal computer 1304. Thus, the processing may include one or moresteps or actions that may be unique to the computer system 1304 asopposed to the device 1308. Thus, the operating system 5508 processesthe event for the computer system 1304, in step 5628, and sends theprocessed or executed actions through the computing system interface5516 to the device interface 5524. The instructions or completedprocessing actions may be received by the receiver 5548 and sent to theinjector 5544. The injector 5544 may send the completed instructions oractions for the personal computer operation system (OS) 5532 to create adisplay or some other output. The personal computer OS 5532 can thendisplay the output, in step 5632. In this way, the device 1308 can bothcontrol the functions of the device 1308 and the personal computer 1304for an event received by the device 1308 but applying to either thedevice 1308 or the personal computer 1304.

An embodiment of a method 5700 for processing an event received on apersonal computer 1304 is shown in FIG. 57. A general order for thesteps of the method 5700 is shown in FIG. 57, but the method may have adifferent order of steps in some embodiments. Generally, the method 5700starts with a start operation 5704 and ends with an end operation 5720.The method 5700 can include more or fewer steps or can arrange the orderof the steps differently than those shown in FIG. 57. The method 5700can be executed as a set of computer-executable instructions executed bya computer system and encoded or stored on a computer readable medium.Hereinafter, the method 5700 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-56.

An event may be received on the personal computer 1304, in step 5708.The event may be as described previously in conjunction with FIG. 56.The event may be received in the user interface of the personal computer1304. Upon receiving the event, the interceptor 5536 may intercept eventinformation from the memory stack of the PC OS 5532 and provide thatinformation to the relay 5540. The relay 5540 may then package theinformation to send to the device, in step 5712. The information may besent in a message provided by the device interface 5524 to the computerinterface 5516 and arriving at the first OS 5508. The first OS 5508 maythen process the event, in step S716. The processing of the event may bethe same or similar as that described in conjunction with FIG. 56.Further, the output provided by the first OS 5508 may then be sent backto the PC OS 5532 as described in conjunction with FIG. 56.

An embodiment of the method 5800 for processing an event that may crossthe personal computer 1304 and device 1308 is shown in FIG. 58. Ageneral order for the steps of the method 5800 is shown in FIG. 58, butthe method may have a different order of steps in some embodiments.Generally, the method 5800 starts with a start operation 5804 and endswith an end operation 5820. The method 5800 can include more or fewersteps or can arrange the order of the steps differently than those shownin FIG. 58. The method 5800 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method5800 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-57.

An event may be received that crosses both the personal computer 1304and the device 1308, in step 5808. For example, a user may desire tomove a window from the device interface to the computer interface bydragging that window from one interface to the other. This type of eventwould cross the boundary of the personal computer 1304 and device 1308and thus create an event that may occur in both the device 1308 and thepersonal computer 1304.

The event may be received in the second OS 5512. Further, theinterceptor 5536 may receive or intercept the event in the personalcomputer OS 5532. The intercepted event may be sent through the relay5540 to the first OS 5508, in step 5812. The first and second OS 5508and 5512 may then communicate about the events to coordinate the timingof the information. Thus, the determination may be made as to where anevent started or stopped and which of the outputs should be processedfirst. Thus, both the second OS 5512 and the first OS 5508 may processthe event or events, in step 5816. The output may then be coordinated soas to provide a seamless user interaction for such an event. The secondOS or the first OS may throttle the other operating system in the device1308 to coordinate or to time the processing and then output of data asdescribed in conjunction with FIG. 56.

An embodiment of the method 5900 for the device 1308 to be master of theunified system, upon docking, as described and shown in FIG. 59. Ageneral order for the steps of the method 5900 is shown in FIG. 59, butthe method may have a different order of steps in some embodiments.Generally, the method 5900 starts with a start operation 5904 and endswith an end operation 5924. The method 5900 can include more or fewersteps or can arrange the order of the steps differently than those shownin FIG. 59. The method 5900 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method5900 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-58.

A docking event may be received, in step 5908. The docking event may becreated when the device 1308 is connected to the computer system 1304 asshown by the line 4912 in FIG. 49. The docking event may occur in boththe computer system 1304 and the device 1308. In the device 1308, thesecond OS 5512 may begin communicating with the first OS 5508 andinstruct the first OS 5508 to begin signaling the computer system 1304to control the computer system's actions. Further, in the computersystem 1304, the application programming interface 5528 may begin to beexecuted and begin scanning or monitoring the stack of the personalcomputer OS 5532 to intercept or inject instructions into the memorystack for the operating system 5532. In embodiments, the first OS 5508may send an instruction to the application programming interface 5528 tobe executed. In other embodiments, the docking signal or event may causethe PC OS 5532 to begin executing the application programming interface5528. Upon the execution of the API 5528 and the first OS 5508, thedevice 1308 controls the personal computer 1304 as the master, in step5912. Thus, any actions being conducted on either the device 1308 or thecomputer system 1304 can be executed or handled with the device 1308.

Upon the device 1308 becoming master over the personal computer 1304,the computer system 1308 subordinates any functions the computer system1308 normally executes independently, in step 5916. For example, anywindows or applications being executed by the personal computer 1304before docking are hidden and those functions are paused while thedevice 1308 is docked. Thus, any functions normally executed on thecomputer system 1304 are subordinated to the master control of thedevice 1308. One such subordination may be the computer system 1304hiding any display, in step 5920. The computer system 1304 displays amaster or unified desktop on the display after having the computersystem's other functions. Any windows or the previous desktop are hiddenbehind the unified system desktop or are replaced by the unified systemdesktop.

Triad Control

An embodiment of the unified system 6000 showing a triad controlinterface 6008 is shown in FIG. 60. The unified system 6000 includes thedevice interface 1304 and the computer system interface 1308. As shownin the device interface 1304, a control window 6004 may be provided byuser interface input or automatically through action of an applicationor other event. The user interface 6004 provides direct access tocertain functionality including, but not limited to, a phoneapplication, an application launcher, a file browser, etc. The providedfunctionality in the unified desktop 6000 may be ported to the computersystem display 1308 in a new and novel user interface area 6008 calledthe triad control. The triad control area 6008 may be a separate popupbar that is navigable by a user interface device, for example, a mouse,that is hovered over a specific area of the user interface 1308. Uponthe recognition that the user desires to view the triad controls 6008,the triad control 6008 may appear on the user interface 1308 as ifsliding from of the screen and onto the top of the display 1308.

The triad control 6008 can include at least some of the samefunctionality as in user interface 6004. For example, the area 6012shows several user selectable icons in the triad control 6008. The userselectable icon 6016 can execute a file browser. The user selectableicon 6020 can execute an application launcher. The user selectable icon6024 can execute an application manager. Further, the user selectableicon 6028 can provide a phone application that is executed by the device1308 but appears on the computer system display 1308. Likewise, a userselectable icon 6032 may provide a browser window that allows the userto browse the internet through the phone device 1308. The selectabledevice icons 6012 provide functionality typically associated with thephone over the unified desktop 6000 by allowing access to thosefunctions using a new selectable area 6012 for user icons in the triadcontrol bar 6008.

A series of windows shown in FIGS. 61A-61C show a visual representationof how the triad control 6008 may be provided to a user in the userinterface 1304. As shown in FIG. 61A, a user interface device 6104 maybe shown in user interface 1308. The user interface device 6104 may becontrollable by a mouse, a finger on a touch sensor display, or by someother hardware means. The represented arrow icon can be moved from thedevice's position, as shown in FIG. 61, to a position shown in FIG. 61B.The position of the user interface device 6104, in FIG. 61B, can berecognized as being within a triad control area 6108. Upon recognizingthe presence and persistence of the user interface device 6104 in thetriad control area 6108, the triad control bar 6008 may begin to presentitself by appearing to slide from the side of the screen. Thus, as thetriad control bar 6008 slides, the triad control bar will becomecompletely displayed, as shown in FIG. 61C. If the user persists inmaintaining the user interface device 6104 in the triad control area6108, the triad control bar 6112 can continue to be displayed and to beselectable for the user.

An embodiment of the application launcher user interface 6204, presentedto the user after user selectable icon 6020 is selected in triad controlbar 6008, is shown in FIG. 62. The user may select the user interfacedevice 6020 or user selectable icon 6020 in the triad control 6008. Uponselecting icon 6020, by user interface action, the application launcheruser interface 6204 may be presented; the application launcher userinterface 6204 presents selectable icons associated with applicationsthat can be launched by the user. The applications may include a firstgroup of one or more applications that are executed on the device and/ora second group of one or more applications executed on the computersystem. Thus, the available applications for the user, presented in theapplication launcher user interface 6204 on the unified desktop,encompass applications executed both on the device and the computersystem. The application launcher user interface 6204 may present thefirst and second group of applications in two, separate sections of theapplication launcher user interface 6024. The first section presentsapplications executed on the device, and the second section presentsapplications executed on the computer system.

For example, the group of applications 6208 provide icons associatedwith PC productivity applications that may be executed by the computersystem. In alternative embodiments, the PC productivity applications6208 are applications executed by the device that may emulate computingsystem functionality. The applications shown in the group 6212 may beANDROID applications or other applications executed solely by thedevice. Thus, by providing the application launcher menu 6204, the usercan select one of the icons shown in either area 6208 or 6212 to launchan application in the unified desktop. Further, the window 6204 mayprovide a search area 6216 where the user may provide search criteriathat can search for a certain application within the applicationlauncher 6204.

An embodiment of a process for using the search function in theapplication launcher user interface 6204 is shown in FIG. 63. The searchfunction can include a user interface 6216 in the application launcheruser interface 6204. The user interface 6216 may accept one or morecharacters of a search string through user interface input from akeyboard, drop down menu, or other user interface action. The searchfunction can be progressive. In other words, as the letters are typedinto the search function user interface, the unified system may searchfor applications containing or starting with the search string. Forexample, the user may have typed a letter “c” 6304 in the search window6216. Upon typing the letter within the search window 6216, the window6204 may present a more limited set of icons associated withapplications that contain or begin with the letter “c.” Thus, based onthe search string, the application launcher presents one or moreselectable icons associated with the search string. For example, thenumber of PC productivity applications shown in area 6208 has beenreduced to the fewer number of applications, as shown in area 6308.Further, the applications shown in area 6212 have been reduced to a lessnumerous number of applications shown in area 6312. The applicationsshown in areas 6308 or 6312 may have a “c” in the name of theapplication or may have a “c” that begins the application name. In thisway, the searching function in 6216 allows for the user to quicklydiscern what applications are important and to select a more limited setof applications from the application launcher window 6204.

Embodiments of a process for using an application manager, initiated byselecting icon 6024, are shown in FIGS. 64 through 66. In embodiments,the user may move a user interface device 6404 to select the applicationmanager icon 6024 in the triad control 6008. At the time of theselection of the icon 6024, the computing system interface 1304 may bedisplaying at least one window 6408 or 6412. Upon selecting theapplication manager icon 6024 in the triad control 6008, a new menu orapplication launcher user interface display 6504 (shown in FIG. 65) maybe presented within the display 1304. The new display 6504 may containtwo or more areas or sections, e.g., area 6516 and area 6520. Theseparation of the areas may be delineated by visual indicia, forexample, a bar 6532 shown between area 6512 and area 6520. Each area6512, 6520 may display different information. The areas 6512 and/or 6520may display one or more representations of one or more applicationsexecuting on the unified system. The one or more representations may bea snapshot(s) of an application window associated with one or moreapplication(s) executing on the unified system. The snapshot may be alast-presented view of the application window on the unified desktop.For example, snapshot 6408 shown in FIG. 65 is the same as or similar towindow 6408 shown in FIG. 64.

Area 6520 of the application launcher user interface 6504 can displayone or more snapshots of applications currently executing or beingdisplayed on the device. Likewise, area 6520 may display one or moresnapshots of applications being executed or being displayed on thecomputing system. For example, windows 6412 and 6408 are shown in area6520. Thus, the display 6504 captures the windows that were currentlybeing displayed in FIG. 64. In further embodiments, an applicationwindow 6524 that was not being displayed but being executed on thedevice may be shown in area 6520. The executed application isrepresented by window representation 6524 in area 6520.

A user may manage the currently executing applications by selecting orconducting user interface actions on the snapshots or representations ofthe applications shown in window or user interface 6504. Thus, if theuser wishes to select, execute, or move the snapshot of a window beingexecuted on the device, e.g., 6508 or 6512, the user may select orconduct the user interface action on those windows 6508, 6512 in area6516. In embodiments, when the user moves a snapshot or user interfacedevice 6604 to select a window 6412 in the display 6504 such that thewindow 6412 may then become displayed in the personal computinginterface 1308, as shown on FIG. 66. If a snapshot is moved betweensections 6516 and 6520, the application window associated with thesnapshot may be moved from the user interface of the device to the userinterface of the computer system, or vice versa. When selected inwindows 6504 and/or windows 6412, the displayed windows in theinterface(s) 1304, 1308 becomes highlighted and/or receives focus. Thus,in embodiments, the application manager window 6504 allows the user tomanage applications currently executing in the unified desktop.

When the user selects the icon 6016, a file manager window 6704 mayappear within the user interface device 1304, as shown in FIG. 67. Thus,the triad control 6008 provides access to files that may be on thedevice or the computer system. The user interface window 6704 mayprovide an area for information about recently-used or recently-openedfiles 6708; the area 6708 displays information associated with recentlyused files (e.g., filename, date when the file was last opened, the sizeof the file, etc.). A file may be associated with an applicationexecuted in the unified system. The icons or user interface devices maybe selectable to open the represented files in area 6708. Further,window 6704 may provide an area 6712 that includes a list of folderseither automatically generated for the user or populated by user input.The folder icons in area 6712 may also be selectable to open a folderand access a file within the data storage of either the device or thecomputer system.

A phone manager user interface 6804 presented, after icon 6028 isselected in the triad control 6008, is shown on FIG. 68. The phonemanager user interface 6804 may allow the user to select one or moreicons displayed within the phone manager user interface 6804 to conducta communication session. For example, the phone icon 6808 may allow theuser to begin a telephone call or send a text message by selecting theicon 6808. Further, in area 6812, a call log may be listed that showsrecent calls either received or sent by the device. In area 6016, one ormore icons may be provided that represent data about frequently calledor contacted persons or entities. In area 6820, one or more contactsthat are communicated with often may be listed in a favorite's field. Infield or area 6824, all contacts may be listed. The list of contacts maybe searchable or navigable by the user in the phone manager userinterface 6804. Any of these different fields may be searchable, bysearch function 6828, presented in the phone manager user interface6804. The user interface of the search function can accept a searchstring and return one or more contacts associated with the searchstring. Each icon, in embodiments, within the phone manager userinterface 6804, may be selectable to conduct a communication sessionusing the device, regardless of the fact that the icon was selected inthe phone manager user interface 6804 presented in the computing systeminterface 1304.

Like the phone functionality described in conjunction with FIG. 68, if auser selects a browser icon 6032 within the triad control bar 6008, abrowser control user interface 6904 may be presented. The browsercontrol user interface 6904 can present one or more items of informationthat are associated with the web browsing functionality of the device.The information is presented as one or more selectable icons. Thus, icon6908 may be selected to begin or conduct a web browser session using theweb browser application and network communication capability of thedevice.

The browser control user interface 6904 can be separated into two ormore areas. For example, area 6912 may include bookmarks for the webbrowser bookmarked by the user in the device. A bookmark is a designatedwebsite that the user may frequent and stores the Uniform ResourceLocator (URL) for the site in the bookmark information. Selecting thebookmark directs the web browser to contact the URL and provide thewebsite information to the user. Area 6916 may provide a list of one ormore names or URLS for the most visited websites that may be selectableby the user. Area 6920 may provide a list of downloads that have beenrecently downloaded by the device from a network. Area 6924 may providea history of recently visited websites using the web browser. Any ofthese areas may be searchable by search function 6928 provided inwindows 6904. Each of the icons within windows 6904 may be selected tobegin a web browsing session using the functionality of the phone, whileselectable within the computer system interface 1304. Any of thedifferent areas may be searchable, by search function 6928, presented inthe browser control user interface 6904. The user interface of thesearch function can accept a search string and return one or morecontacts associated with the search string.

An embodiment of a method 7000 for selecting or executing functionswithin the unified desktop using the triad control 6008 is shown in FIG.70. An embodiment of the method 7000 for receiving an event for theunified desktop at the device 1308 is shown in FIG. 70. While a generalorder for the steps of the method 7000 is shown in FIG. 70. Generally,the method 7000 starts with a start operation 7004 and ends with an endoperation 7036. The method 7000 can include more or fewer steps or canarrange the order of the steps differently than those shown in FIG. 70.The method 7000 can be executed as a set of computer-executableinstructions executed by a computer system and encoded or stored on acomputer readable medium. Hereinafter, the method 7000 shall beexplained with reference to the systems, components, modules, software,data structures, user interfaces, etc. described in conjunction withFIGS. 1-69. The method 7000 may be described with particular attentionpaid to FIGS. 60 through 69.

A user interface event may be received in display 1304, in step 7080.The user interface event may occur within the triad control region 6108.Upon receiving the user interface action that persists within the area6108, the unified desktop may display a triad control 6008, in step7012. In embodiments, the triad control 6008 display may be conducted asdescribed in conjunction with FIGS. 61A through 61C.

Thereinafter, the unified desktop system may determine if an event isconducted within the triad control bar 6008. An event may be a selectionof a user selectable icon within region 6012 or some other iconpresented within the triad control 6008. If no action is conducted, thetriad control 6008 may continue to be displayed on user interface device1308, in step 7028. If an event does occur within the triad control6008, such as the selection of one of the user selectable icons in area6012, the selected function may be provided in step 7020.

The function provided may be the display of a window as described inconjunction with FIG. 62 through 69. The menus provided may includefurther functionality that may be accessed through the triad control6008. The unified desktop must then determine if a UA device is still inthe triad control 6008 or in one of the menus provided from the triadcontrol 6008, in step 7024. If the user interface device remains withinthe triad control area 6008, the triad control 6008 may continue to bedisplaced, in step 7028. However, if the user interface device is nolonger within the triad control area 6008, the triad control 6008 may behidden, in step 7032. If a functionality provided within the menu isselected by a user, for example, selecting a user selectable icon withina menu presented in FIGS. 62 through 69, the triad control may be hiddenand the function provided.

An embodiment of a method 7100 for providing application managerinterfaces within the unified desktop is shown in FIG. 71. A generalorder for the steps of the method 7100 is shown in FIG. 71, but themethod may have a different order of steps in some embodiments.Generally, the method 7100 starts with a start operation 7104 and endswith an end operation 7128. The method 7100 can include more or fewersteps or can arrange the order of the steps differently than those shownin FIG. 71. The method 7100 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method7100 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-70 and. The method 7100 may be described withparticular attention paid to FIGS. 60 through 70.

As explained in FIGS. 1 through 70, a device 100 and computer system1104 may be provided. The device 100 may then be docked with thecomputer system 1104 to form a unified system 1100 consisting of thedevice 100 and the computer system 1104. When the device 100 is docked,the device 100 and computer system 1104 respond in generating a unifieddesktop 1300 for the unified system 1100. The unified desktop 1300 is asingle logical display that spans both the user interface 1308associated with the device 100 and the user interface 1304 associatedwith the computer system 1104. The unified desktop 1300 can emulate apersonal computer environment where windows and applications may beexecuted and information may be displayed on the unified desktop 1300for the user.

The unified system 1100 can receive a user interface event, which may bea user interface input into the first user interface 1308 associatedwith the device 100, in step 7108. The user interface input can be aselection of a triad control button 6008 or other control button(s)associated with the device 100 or computer system 1104. The buttons mayprovide the ability to display an application manager interface 7212, instep 7112. Thus, in response to receiving the user interface input theunified system 1100 can display a first application manager interface7212 on the device 100. Optionally, a second user interface input may bereceived, in step 7116. The second user interface input may be an inputinto the second user interface 1304 of the computer system 1104. Inresponse to the second user interface input, a second applicationmanager interface 7216 may be shown on the computer system interface1304. It should be noted that it is possible for one user interfaceinput to force the display of both application manager interface 7212and application manager interface 7216 with a single input orinteraction.

As shown in FIG. 73, the application manager interfaces 7212 and 7216may display at least one or more of the active windows 7304, 7308, 7312,7316, and/or 7320 on either the first user interface 1304 or the seconduser interface 1308. As explained previously herein, the applicationmanager interface 7212, 7216 may be used to reorder the display ofwindows in either the device user interface 1308 or the computer systemdisplay 1304. For example, as shown in FIG. 74, with a user interfaceinput 7404, 7408, window 7308 may be brought to the foreground in frontof window 7304, which changes the display 1304, as shown in FIG. 73, towhat is shown in FIG. 74. Thus, the unified system 1100 can receive athird user interface input to reorder one or more applicationrepresentations or thumbnails 7324-7364, such as window 7308 and/orwindow 7304, in the first application interface 7212 and/or the secondapplication interface 7216, in step 7124.

The third user interface input 7404, 7408 can be a drag and drop or aflick gesture as described in conjunction with FIGS. 4A through 4H. Forexample, arrow 7408 can represent a switch in the orientation of thethumbnails or representations 7356 and 7360 that are associated withwindows 7304 and 7308, respectively, in the application managerinterface(s) 7212, 7216. In this case, window representation 7360 ismoved in front of window representation 7356. This user interface input7408 can change the display of the application windows 7304 and 7308 indisplay 1304 in the computer system 1104.

Any change in one of the application manager interfaces 7212 and/or 7216can change the other representations 7324-7364 in the other applicationmanager interface 7212 and/or 7216. For example, the change 7408 canalso change the representation of windows 7332 and 7336. Likewise, areorientation 7404 in the other application manager interface 7216 canchange the window representations for 7308 and 7304 and therepresentation of the windows in application manager interface 7212.

In embodiments, the third user interface can be an input into the touchsensitive display 1308. Thus, a drag and drop or flick gesture may movethe windows in the first user interface 1308 and change therepresentation of the windows in the application manager interface 7212,7216. The third user interface input may also be a gesture in a gesturecapture region 120, 124 as explained herein. Likewise, changes in theuser interface 1304 can also change the application manager interface7212, 7216. For example, window six may receive focus by a user clickingon the window 7308 with a device (e.g. mouse) and bringing the window7308 into the foreground over windows 7304 and 7312. This change infocus may also change the order or representation of the windows inapplication manager interfaces 7212 and 7216.

The applications in the unified desktop 1300 may have different typesthat are based on where the windows 7308-7320 are displayed. Forexample, applications displayed in user interface 1304 may be devicefocused applications. In contrast, applications displayed on userinterface 1308 may be considered computer system focused applications. Adevice focused application can be an application that is executed on thedevice 100. A computer system focused application can be an applicationthat may be executed in either the computer system 1104 or the device100 but is displayed on the computer system interface 1304.

A third user interface input that changes the representation of theapplication manager interface 7212, 7216 may attempt to change acomputer system focused application to a device focused application. Thethird user interface input may attempt to change the computer systemfocused application to a device focused application and may be preventedby the unified desktop 1300. Thus, the unified desktop 1300 does notmove the window as specified by the user interface input and may returnan error message to the user in one or more of the displays 1304, 1308.

A fourth user input may be received that changes a computer systemfocused application to a device focused application. In this situation,a window may be moved from the computer system display 1304 to thedevice display 1308. For example, as shown in FIG. 75, the window 6 7308may be moved from the computer system display 1304 to the device display1308. The application manager interface 7216 on the computer system 1104may be updated to show that window 7308 is now on the device interface1308 and not on the computer system interface 1304. The change may alsobe shown in the device 100 application manager interface 7212. Thefourth user interface input that makes the change in the applicationwindow 7308 can be a drag and drop, from one interface 1304 to the otherinterface 1308, may be a change in one or more of the applicationmanager interfaces 7216 or 7212, or some other input that changes thepositioning of window 7308.

A fifth user interface input may be received that reorders the windowstack of the device 100 as represented in one or more of the applicationmanager interfaces 7212, 7216. For example, as shown in FIG. 76, achange may be made that repositions window 1 7320 and window 2 7316. Thechange may be made in one of the application manager interfaces 7212,7216. For example, a drag and drop or a flick gesture of the thumbnail7316 or 7320 may be done in the application manager interface 7216 tochange the position of the windows on the device 100. The change maythen be shown in application manager interface 7212. This process mayalso be completed in the device 100 application manager interface 7212and then shown in the application manager interface 7216.

An embodiment of a method 7700 for providing application managerinterfaces within the unified desktop is shown in FIG. 77. A generalorder for the steps of the method 7700 is shown in FIG. 77, but themethod may have a different order of steps in some embodiments.Generally, the method 7700 starts with a start operation 7704 and endswith an end operation 7728. The method 7700 can include more or fewersteps or can arrange the order of the steps differently than those shownin FIG. 77. The method 7700 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method7700 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-76. The method 7700 may be described withparticular attention paid to FIGS. 60 through 76.

A method 7700 may also be provided where the first application managerinterface 7316 is displayed, in step 7712, in the first user interface1308 presented on the device 100 after receiving a first user interfaceinput, in step 7708, into either the first user interface 1308 or thesecond user interface 1304 associated with the computer system 1104, instep 7708. Optionally, a second user interface input may be received ineither the first or second user interfaces 1304, 1308 associated witheither the device 100 or the computer system 1104, in step 7716. Thesecond user interface input may cause the unified desktop 1300 todisplay the second application manager interface 7216 in the computersystem display 1304, in step 7720. However, in this process 7700, athird user interface input may reorder one or more thumbnails 7304-7320in the second application manager user interface 7216, in step 7724.

The third user interface input may not affect one or more applicationwindows associated with the reordered thumbnails in the applicationmanager user interface 7216. For example, as shown in FIG. 78, thethumbnail 7332 may be moved to a different orientation in theapplication manager interface 7216 compared to window representation7308. However, within the user interface 1304 no change is made ascompared to the original user interface shown in FIG. 73. Thus, it ispossible to reorder thumbnails 7324-7364 of the windows 7304-7320 in theapplication manager interfaces 7216 and 7212 without changing theorientation of the windows 7304-7320 in the user interfaces 1304 and1308.

However, reordering thumbnails 7324-7364 in one user application managerinterface 7216 or 7212 can reorder those same thumbnails 7324-7364 inthe other application manager interface 7212 or 7216. In this way, thethumbnails 7344-7364 in the first application manager interface 7212 andthe thumbnails 7324-7340 in the second application manager interface7216 stay the same or similar.

Further, the application manager interfaces 7212 and 7216 may displaythumbnails or representations for all executing applications. However,the display area for the application manager interfaces 7212 and 7216may not be large enough to display all of the thumbnails at the sametime but may present a navigable user interface 7212 and 7216. Thus, byusing a swipe, drag and drop, or other gesture or another user interfaceinput described herein, the user may scroll through the thumbnails7324-7364 in those application manager interfaces 7212 and 7216.

In the unified desktop 1300, a first application window 7304 may bedisplayed on the first user interface 1304. Likewise, a secondapplication 7316 may be displayed in the second user interface 1308. Asexplained previously, the second application 7316 may be a devicefocused application while the first application 7304 may be computersystem focused application. The device focused application 7316 shown inthe second user interface 1308 and the computer system focusedapplications 7304-7312 in the first user interface 1304 can be displayeddifferently in the application manager user interfaces 7216, 7216. Forexample, the set of application representations 7332-7340 and 7356-7364are associated with the computer system applications 7304-7312 on thefirst user interface 1304. These thumbnails 7332-7340 and 7356-7364 showa darkened dotted box, which delineates the thumbnails as being computersystem applications and/or displayed on the first user interface 1304.Other visual indicia may be used besides the dotted black line as thedotted black line is only provided as an example of how different typesof thumbnails may be displayed differently.

Further, the computer system thumbnails 7332-7340 and 7356-7364 may bedifferently positioned than the thumbnails representing device focusedapplication. For example, in the first application manager userinterface 7212, the thumbnails 7332-7340 and 7356-7364 are shown to theright on a second user interface 114 of the device display 1308. Thethumbnails 7344-7352 for the device focused applications may bedisplayed to the left or on a first user interface 110 of the devicedisplay 1308.

Likewise, the thumbnails 7324-7328 for device focused applications maybe shown at the top of the second application manager user interface7216 and separated by a line 7804. The computer system applicationthumbnails 7332-7340 may be shown at the bottom or below the line 7804of the second application user interface 7216.

The second application 7316 may be an ANDROID application. The firstapplication 7304 may be an ANDROID application and/or a personalcomputer productivity application. An ANDROID application could be anyapplication that executes in the ANDROID or ANDROID-similar computersystem 1104 or operating system. A personal computer productivityapplication can be any application that typically executes on a personalcomputer 1104.

An embodiment of a method 7900 for providing application managerinterfaces within the unified desktop is shown in FIG. 79. A generalorder for the steps of the method 7900 is shown in FIG. 79, but themethod may have a different order of steps in some embodiments.Generally, the method 7900 starts with a start operation 7904 and endswith an end operation 7928. The method 7900 can include more or fewersteps or can arrange the order of the steps differently than those shownin FIG. 79. The method 7900 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method7900 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-78. The method 7900 may be described withparticular attention paid to FIGS. 60 through 78.

Another method 7900 may provide for a device 100 and a computer system1104 that are docked to form a unified system 1100. A unified desktop1300 may be generated to for the unified system 1100 that provides forthe first user interface 1308 and a second user interface 1304 beingpart of the unified desktop 1300, where the unified desktop 1300emulates a personal computer environment. Thus, the unified system 1100can receive an indication that the device 100 is docked with thecomputer system 1104, in step 7908. The unified system 1100 can thengenerate the unified desktop 1300, in step 7912.

Thereinafter, the unified desktop 1300 may receive a first input as auser interface event that moves the display window associated with anapplication from the device user interface 1308 to the computer systemuser interface 1304, in step 7916. As explained previously, applicationsdisplayed on the display 1308 are device focused applications. Whenmoving a device focused application to the computer system userinterface 1304, the unified system 1100 must determine if thatapplication being executed on a device 100 is associated with a bigbrother application normally associated with the computer system 1104,in step 7920.

A big brother application is an application that is normally executed inthe computer system 1104 that has functionality similar to at least oneapplication executed by the device 100. For example, a TWITTERapplication run in an ANDROID environment on the device 100 may have abig brother application for TWITTER that is typically run in a computersystem environment on the personal computer 1104. Thus, the big brotherapplication is the application on the computer system 1104 that isassociated with the application executed on the device 100.

These big brother applications may be associated with the deviceapplications to provide a seamless transition when moving applicationwindows in the unified system 1100. If the device application isassociated with a big brother application, the device 100 may send adirective to the computer system 1104 to begin execution of the bigbrother application, in step 7924. The directives are sent as explainedherein to execute different functions in the unified system 1100.

Thereinafter, the computer system 1104 may receive, from the device 100,state information, in step 7928. State information can be informationthat describes the current state of the application was when it wasexecuting on the device 100. For example, the state information can havea configuration of the display or any information that is being storedin memory that will be needed by the computer system 1104 to continueexecution of the application. The state information is extracted at thepoint that the application was moved to the computer system display1304. Examples of state information for a web browser application may bethe current site or URL that had been navigated to for the web browser.Further, any information currently entered into a user interfaceassociated with the web browser may also be provided to the computersystem 1104. Other applications may have different, less, or more stateinformation transferred from the device 100 to the computer system 1104.

Once the state information is received or at some point after thedetermination is made that a big brother application is associated withthe device application, the computer system 1104 can re-execute thedevice application as a big brother application, in step 7932. Thus, thebig brother application is executed and emulates the application fromthe device 100 and provides the appearance that the application windowwas seamlessly moved from the device 100 to the computer system 1104.

The input that causes the big brother application to execute may be thedocking of the device 100. Thus as explained herein before, the dockingof the device 100 may cause one or more windows to move from the devicedisplay 1308 to the computer system display 1304. In other embodiments,the first input that moves the window may be a user interfaceinteraction, such as a drag and drop or other type of user interfaceinteraction, which moves the display from the first user interface 1308to the second user interface 1304.

The directive sent from the device 100 to the computer system 1104 maybe a command from the device 100 to the computer system 1104 to executethe big brother application. As explained with the device 100 beingmaster and the computer system 1104 being subordinate to the device 100during execution of the unified system 1100, the device 100 can commandthe computer system 1104 to complete certain functions. In this case,the device 100 may command the computer system 1104 to execute the bigbrother application. The state information may follow the directive in asecond message after the directive has been sent. In this way, thecomputer system 1104 may begin executing the big brother application, atleast in a general sense, before receiving the state information toconfigure the big brother application into a common state as was shownon the device 100 before the window was moved.

Examples of the execution of big brother applications are shown in FIGS.80 and 81. In this example, at least two applications 8004 and 8008 arebeing executed on the device 100 and shown in the device display 1308.There are no current executing applications shown in the computer systemdisplay 1304. At some point, due to a user interface input or otherevent, the applications 8004, 8008, being executed on the device 100,are moved to the computer system display 1304, as shown in FIG. 81.While the two application windows 8004, 8008 may be similar to what wasshown in the device 100, the application windows 8004, 8008 are executedin big brother applications on the computer system 1104. For example,the web browser function 8008 being executed in the device 100 is nowbeing executed in a computer system web browser application. Likewise,the TWITTER application 8004 executed in the device 100 is now beingexecuted as a TWITTER application on the computer system after beingmoved to the computer system display 1308.

An embodiment of a method 8200 for providing the unified desktop isshown in FIG. 82. A general order for the steps of the method 8200 isshown in FIG. 82, but the method may have a different order of steps insome embodiments. Generally, the method 8200 starts with a startoperation 8204 and ends with an end operation 8228. The method 8200 caninclude more or fewer steps or can arrange the order of the stepsdifferently than those shown in FIG. 82. The method 8200 can be executedas a set of computer-executable instructions executed by a computersystem and encoded or stored on a computer readable medium. Hereinafter,the method 8200 shall be explained with reference to the systems,components, modules, software, data structures, user interfaces, etc.described in conjunction with FIGS. 1-81. The method 8200 may bedescribed with particular attention paid to FIGS. 60 through 81.

Method 8200 may begin when the indication is received by the device 100or computer system 1104 that the device 100 is docked with the computersystem 1104, in step 8208. Thus, the device 100 and computer system 1104are provided and then docked to form a unified system 1100. The unifiedsystem 1100 can then generate the unified desktop 1300, in step 8212.The unified desktop 1300 is a common display that covers both thedisplay 1308 of the device 100 and the display 1304 of the computersystem 1104. This unified desktop 1300 emulates a personal computerenvironment.

Thereinafter, a user interface event or other input may be received thatmoves the display of an application from the device user interface 1308to the computer system interface 1304 (see FIGS. 79-81). The applicationdisplay may be associated with an application that was originallyexecuted on the device 100. The device 100 must then determine, for theunified system 1100, whether the application is associated with the bigbrother application.

To begin the determination, the device 100 can search metadata 8300,shown in FIG. 83, associated with a big brother application pool todetermine if there is an associated big brother application, in step8220. A big brother application pool can be a set of one or moreapplications that are associated with one or more device 100applications. The computer system applications in the big brotherapplication pool may emulate or have similar features or functions todevice applications and present a set of big brother applications.

The metadata 8300 associated with the big brother application pool maybe as shown in FIG. 83 in the data structure 8304. The data structure8304 shown in FIG. 83 may be any type of database or other data storagetechnique or structure that allows for the metadata 8300 or informationto be searched, stored, and retrieved for use in various functions.

The unified system 1100 can use the big brother application poolmetadata 8300 to determine if an application is part of a big brotherapplication pool, in step 8224. Thus, if the device 100 application isassociated with a big brother application, the method 8200 may proceedYES to step 8228 where the big brother application is executed and theapplication for the device 100 is moved into the big brotherapplication. If there is no big brother application, the method 8200 mayproceed NO to execute the application in a freeform window, in step8232. A freeform window is a type of logical structure within theunified system 1100 that allows for device applications to be executedin the computer system 1104 environment without having a big brotherapplication.

As shown in the data structure 8304, the big brother application poolcan include two or more big brother applications. The data structure caninclude more or less data and have more or fewer entries than that shownin FIG. 83, as represented by ellipses 8348 and 8352. Each big brotherapplication, in the big brother application pool, can be associated withat least one application executed on the device 100. For example, in row8308, device application 1 is associated with big brother application W.Thus, the unified system 1100 can search the metadata within the row8308 of the associated applications to determine that the device 100application 1 is associated with big brother application W.

The metadata 8300 can include the association as shown in column 8312.Column 8312 can have a simple indication as to whether or not there isan association for the device application in column 8316. The column8312 can be searched quickly as it is binary, for the unified system1100 to determine if the device application, shown in column 8316, hasan associated big brother application in column 8320. If there is anassociation, a third column 8328 may identify which big brotherapplications are associated with the device application in column 8316.

The associations between the device applications, in column 8316, andthe big brother applications, shown in column 8324 may be createdautomatically or manually. Thus, there may be a simple indicationautomatically provided to help a user make the association. For example,a simple name of the application may be enough to determine if there isan association between a device application and a big brotherapplication. In other situations, a user or system administrator may beable to make the associations manually by providing the metadata or theassociation to the data structure 8304. The user may manually set anassociation between, for example, application 8332 and big brotherapplication 8336.

The device 100 may search the metadata within the data structure 8304.As the device 100 may be master, the device 100 may determine if thereis a big brother application. As such, if the device 100 does determinethere is a big brother application associated with the deviceapplication whose display is moved to the computer system display 1304,the device 100 can send a directive to the computer system 1104 toexecute the big brother application identified or associated with themetadata 8300, in the data structure 8304. Thus, the device 100 can readthe identifier, in column 8324, and send that information to thecomputer system 1104 to execute that big brother application. Further,the device 100 may read the state information included in column 8328 todetermine what state information to send to the computer system 1104 toproperly execute the window in display 1304.

An application may be introduced to either a device 100 or the computersystem 1104. When a new application or some other change to theconfiguration of the device 100 or computer system 1104 is made, a newassociation between a device application and a big brother applicationmay be made. For example, if application 8340 is recently introduced tothe device 100, the device 100 may automatically determine that there isa big brother application, application 8344 on the computer system 1104that should be associated as a big brother application. Thus, if a newapplication is installed, the device 100 may create a new row or item inthe data structure 8304 making the association and determining themetadata for the association in the data structure 8304.

While the exemplary aspects, embodiments, and/or configurationsillustrated herein show the various components of the system collocated,certain components of the system can be located remotely, at distantportions of a distributed network, such as a LAN and/or the Internet, orwithin a dedicated system. Thus, it should be appreciated that thecomponents of the system can be combined in to one or more devices, suchas a tablet-like device, or collocated on a particular node of adistributed network, such as an analog and/or digital telecommunicationsnetwork, a packet-switch network, or a circuit-switched network. It willbe appreciated from the preceding description, and for reasons ofcomputational efficiency, that the components of the system can bearranged at any location within a distributed network of componentswithout affecting the operation of the system. For example, the variouscomponents can be located in a switch such as a PBX and media server,gateway, in one or more communications devices, at one or more users'premises, or some combination thereof. Similarly, one or more functionalportions of the system could be distributed between a telecommunicationsdevice(s) and an associated computing device.

Furthermore, it should be appreciated that the various links connectingthe elements can be wired or wireless links, or any combination thereof,or any other known or later developed element(s) that is capable ofsupplying and/or communicating data to and from the connected elements.These wired or wireless links can also be secure links and may becapable of communicating encrypted information. Transmission media usedas links, for example, can be any suitable carrier for electricalsignals, including coaxial cables, copper wire and fiber optics, and maytake the form of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Also, while the flowcharts have been discussed and illustrated inrelation to a particular sequence of events, it should be appreciatedthat changes, additions, and omissions to this sequence can occurwithout materially affecting the operation of the disclosed embodiments,configuration, and aspects.

In yet another embodiment, the systems and methods of this disclosurecan be implemented in conjunction with a special purpose computer, aprogrammed microprocessor or microcontroller and peripheral integratedcircuit element(s), an ASIC or other integrated circuit, a digitalsignal processor, a hard-wired electronic or logic circuit such asdiscrete element circuit, a programmable logic device or gate array suchas PLD, PLA, FPGA, PAL, special purpose computer, any comparable means,or the like. In general, any device(s) or means capable of implementingthe methodology illustrated herein can be used to implement the variousaspects of this disclosure. Exemplary hardware that can be used for thedisclosed embodiments, configurations and aspects includes computers,handheld devices, telephones (e.g., cellular, Internet enabled, digital,analog, hybrids, and others), and other hardware known in the art. Someof these devices include processors (e.g., a single or multiplemicroprocessors), memory, nonvolatile storage, input devices, and outputdevices. Furthermore, alternative software implementations including,but not limited to, distributed processing or component/objectdistributed processing, parallel processing, or virtual machineprocessing can also be constructed to implement the methods describedherein.

In yet another embodiment, the disclosed methods may be readilyimplemented in conjunction with software using object or object-orientedsoftware development environments that provide portable source code thatcan be used on a variety of computer or workstation platforms.Alternatively, the disclosed system may be implemented partially orfully in hardware using standard logic circuits or VLSI design. Whethersoftware or hardware is used to implement the systems in accordance withthis disclosure is dependent on the speed and/or efficiency requirementsof the system, the particular function, and the particular software orhardware systems or microprocessor or microcomputer systems beingutilized.

In yet another embodiment, the disclosed methods may be partiallyimplemented in software that can be stored on a storage medium, executedon a programmed general-purpose computer with the cooperation of acontroller and memory, a special purpose computer, a microprocessor, orthe like. In these instances, the systems and methods of this disclosurecan be implemented as a program embedded on personal computer such as anapplet, JAVA® or CGI script, as a resource residing on a server orcomputer workstation, as a routine embedded in a dedicated measurementsystem, system component, or the like. The system can also beimplemented by physically incorporating the system and/or method into asoftware and/or hardware system.

Although the present disclosure describes components and functionsimplemented in the aspects, embodiments, and/or configurations withreference to particular standards and protocols, the aspects,embodiments, and/or configurations are not limited to such standards andprotocols. Other similar standards and protocols not mentioned hereinare in existence and are considered to be included in the presentdisclosure. Moreover, the standards and protocols mentioned herein andother similar standards and protocols not mentioned herein areperiodically superseded by faster or more effective equivalents havingessentially the same functions. Such replacement standards and protocolshaving the same functions are considered equivalents included in thepresent disclosure.

The present disclosure, in various aspects, embodiments, and/orconfigurations, includes components, methods, processes, systems and/orapparatus substantially as depicted and described herein, includingvarious aspects, embodiments, configurations embodiments,subcombinations, and/or subsets thereof. Those of skill in the art willunderstand how to make and use the disclosed aspects, embodiments,and/or configurations after understanding the present disclosure. Thepresent disclosure, in various aspects, embodiments, and/orconfigurations, includes providing devices and processes in the absenceof items not depicted and/or described herein or in various aspects,embodiments, and/or configurations hereof, including in the absence ofsuch items as may have been used in previous devices or processes, e.g.,for improving performance, achieving ease and\or reducing cost ofimplementation.

The foregoing discussion has been presented for purposes of illustrationand description. The foregoing is not intended to limit the disclosureto the form or forms disclosed herein. In the foregoing DetailedDescription for example, various features of the disclosure are groupedtogether in one or more aspects, embodiments, and/or configurations forthe purpose of streamlining the disclosure. The features of the aspects,embodiments, and/or configurations of the disclosure may be combined inalternate aspects, embodiments, and/or configurations other than thosediscussed above. This method of disclosure is not to be interpreted asreflecting an intention that the claims require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive aspects lie in less than all features of a singleforegoing disclosed aspect, embodiment, and/or configuration. Thus, thefollowing claims are hereby incorporated into this Detailed Description,with each claim standing on its own as a separate preferred embodimentof the disclosure.

Moreover, though the description has included description of one or moreaspects, embodiments, and/or configurations and certain variations andmodifications, other variations, combinations, and modifications arewithin the scope of the disclosure, e.g., as may be within the skill andknowledge of those in the art, after understanding the presentdisclosure. It is intended to obtain rights which include alternativeaspects, embodiments, and/or configurations to the extent permitted,including alternate, interchangeable and/or equivalent structures,functions, ranges or steps to those claimed, whether or not suchalternate, interchangeable and/or equivalent structures, functions,ranges or steps are disclosed herein, and without intending to publiclydedicate any patentable subject matter.

What is claimed is:
 1. A method, comprising: providing a devicecomprising a first processor, a first memory, and a first screen;providing a computer system comprising a second processor, a secondmemory, and a second screen; docking the device to the computer systemto form a unified system the unified system comprising the device andthe computer system, wherein the device comprises a master of theunified system and the computer system comprises a subordinate of theunified system, and wherein, as the subordinate of the unified system,in response to docking the device, the computer system hides all userinterface windows that were presented by the computer system beforedocking and pauses execution of all applications that were executing onthe computer system before docking and presents a desktop interface;generating a unified desktop for the unified system on the display ofthe computer system, wherein the unified desktop is a user interfacehaving a first and second portion, the first portion includes at least afirst user interface associated with and presented by the device and thesecond portion includes at least the desktop interface associated withand presented by the computer system; executing a first instance of afirst application on the device, the first application having anapplication display associated with the application displayed on thefirst user interface, wherein the first application is executed in amobile computing environment; receiving a first input, wherein the firstinput moves the application display of the first application from thefirst user interface to the desktop interface; in response to the firstinput: the device, in control of the unified system, sending adirective, in a first message, to the computer system to execute a bigbrother application associated with the first application on thecomputer system; in response to the directive from the device, thecomputer system executing the big brother application, wherein the firstapplication and big brother application provide similar but differentfunctionality, and wherein the big brother application is executed in apersonal computer environment; after sending the directive, the device,in control of the unified system, accessing a data structure, stored atthe device, to determine what information about the first instance isrequired by the big brother application to continue execution of thefirst instance in the big brother application, wherein accessing thedata structure includes: locating by the device an association betweenthe first application and the big brother application; based on locationof the association, retrieving by the device state information metadataassociated with the association between the first application and thebig brother application; sending by the device a second messagetransferring the state information about the first instance from thedevice to the big brother application executing on the computer systemto continue execution of the first instance in the big brotherapplication; and displaying the application display on the desktopinterface.
 2. The method of claim 1, wherein the big brother applicationis associated with a personal computer environment and the firstapplication is associated with a mobile device environment.
 3. Themethod of claim 2, further comprising determining if a big brotherapplication is associated with the first application.
 4. The method ofclaim 3, wherein the device functions as the master device in theunified system.
 5. The method of claim 4, wherein the computer systemfunctions as the slave device in the unified system.
 6. The method ofclaim 5, wherein the state information includes at least a current stateof the first application before being moved to the desktop interface. 7.The method of claim 6, wherein the first input is the docking of thedevice and the first instance of the first application is automaticallymoved to the second screen in response to the docking.
 8. The method ofclaim 7, wherein the first input is a user interface input that movesthe application display from the first user interface to the desktopinterface.
 9. The method of claim 8, wherein the directive is a commandfrom the device to the computer system to execute the big brotherapplication.
 10. The method of claim 9, wherein the state informationconfigures the already executing big brother application.
 11. A unifiedsystem, comprising: a device comprising: a first screen; a first memory;a first processor; a computer system comprising: a second screen; asecond memory; a second processor, wherein the device is docked with thecomputer system to form the unified system, wherein the device comprisesa master of the unified system and the computer system comprises asubordinate of the unified system, and wherein, as the subordinate ofthe unified system, in response to docking the device, the computersystem hides all user interface windows that were presented by thecomputer system before docking and pauses execution of all applicationsthat were executing on the computer system before docking and presents adesktop interface; wherein the unified system is configured to: generatea unified desktop for the unified system on the display of the computersystem, wherein the unified desktop is a user interface having a firstand second portion, the first portion includes at least a first userinterface associated with and presented by the device and the secondportion includes at least the desktop interface associated with andpresented by the computer system, and wherein the unified desktopemulates a personal computer environment; executing a first instance ofa first application on the device, the first application having anapplication display associated with the application displayed on thefirst user interface, wherein the first application is executed in amobile computing environment; receive a first input, wherein the firstinput moves the application display of the first application from thefirst user interface to the desktop interface; in response to the firstinput: send by the device a directive, in a first message, to thecomputer system to execute a big brother application associated with thefirst application on the computer system; in response to the directivefrom the device, execute by the computer system the big brotherapplication, wherein the first application and big brother applicationprovide similar but different functionality, and wherein the big brotherapplication is executed in a personal computer environment; aftersending the directive, access by the device a data structure todetermine what state information about the first instance is required bythe big brother application to continue execution of the first instancein the big brother application, wherein when accessing the datastructure the unified system is configured to: locate by the device anassociation between the first application and the big brotherapplication; based on location of the association, retrieve by thedevice state information metadata associated with the associationbetween first application and the big brother application; send by thedevice a second message transferring the state information about thefirst instance to the big brother application to continue execution ofthe first instance in the big brother application; and displaying theapplication display on the desktop interface.
 12. The unified system ofclaim 11, wherein the big brother application is associated with apersonal computer environment and the first application is associatedwith a mobile device environment.
 13. The unified system of claim 11,wherein the unified system is further configured to receive the stateinformation for the first application, wherein the state informationincludes at least a current state of the first application before beingmoved to the desktop interface.
 14. The unified system of claim 11,wherein the directive is a command from the device to the computersystem to execute the big brother application.
 15. The unified system ofclaim 11, wherein the first input is one of a docking of the device thatautomatically moves the first instance or a user interface input thatmoves the first instance from the first user interface to the desktopinterface.
 16. A computer-readable, non-transitory medium comprising aset of instructions stored therein which, when executed by a processor,causes the processor to: form, in response to docking a device to acomputer system, a unified system, the unified system comprising thedevice and the computer system, wherein the device comprises a master ofthe unified system and the computer system comprises a subordinate ofthe unified system, and wherein, as the subordinate of the unifiedsystem, in response to docking the device, the computer system hides alluser interface windows that were presented by the computer system beforedocking and pauses execution of all applications that were executing onthe computer system before docking and presents a desktop interface;generate a unified desktop for the unified system on the display of thecomputer system, wherein the unified desktop is a user interface havinga first and second portion, the first portion includes at least a firstuser interface associated with and presented by the device and thesecond portion includes at least the desktop interface associated withand presented by the computer system; execute a first instance of afirst application on the device, the first application having anapplication display associated with the application displayed on thefirst user interface, wherein the first application is executed in amobile computing environment; receive a first input, wherein the firstinput moves the application display of the first application from thefirst user interface to the desktop interface; in response to the firstinput: the device, in control of the unified system, sending adirective, in a first message, to the computer system to execute a bigbrother application associated with the first application on thecomputer system; in response to the directive from the device, thecomputer system executing the big brother application, wherein the firstapplication and big brother application provide similar but differentfunctionality, and wherein the big brother application is executed in apersonal computer environment; after sending the directive, the device,in control of the unified system, accessing a data structure, stored atthe device, to determine what information about the first instance isrequired by the big brother application to continue execution of thefirst instance in the big brother application, wherein accessing thedata structure includes: locating by the device an association betweenthe first application and the big brother application; based on locationof the association, retrieving by the device state information metadataassociated with the association between the first application and thebig brother application; sending by the device a second messagetransferring the state information about the first instance from thedevice to the big brother application executing on the computer systemto continue execution of the first instance in the big brotherapplication; and displaying the application display on the desktopinterface.